no longer be an issue. Of course that means not exporting _any_
C++ classes, which is an excellent idea in its own right...
The real misconception here is that "Specified Procedure not found" means
what it says, which is not the case and is one of main problems with
regsvr32
and is still present in .net. When the dll is loaded and one of the
dependancies can not be found, rather then tell you the first dll that can
be
loaded it returns this type of message, which will set you off in a
totally
wrong direction.
In this case it was much worse. The real problem was the dll that was
being
registered was using older dlls that had been created with VC 6.0. Now
starting with VC2005 you have the option to treat wchar_t as a built_in
type.
This mangles the entry point names differently than when it is NOT a built
in
type. This has a HUGE implication when converting cpp programs from vc2003
or
earlier to vc2005 or later. If ANY of the return or calling parameters
contain wchar_t types and you are treating wchar_t as a native type the
mangling will not match and you will get the "Specified procedure not
found"
error.
So you say, just set the flag to not treat wchar_t as built in types. On
the
surface this sounds reasonable, however, since you are using REGSVR32 that
means that your program is COM and will probably be using the standard COM
or
ATL support libraries which have all of their compiles done with wchar_t
treated as a build in type and now you are stuck. You don't get to have it
both ways.
This is a real problem that I have not been able to resolve. Why the
mangling needs to be different whether wchar_t is a built in type or not
is
beyond me.
--
Scott Norberg
"Charles Wang[MSFT]" wrote:
Hi Scott,
From your description, it seemed that this was a DLL deployment issue. I
noticed that you directly copied the DLLs from the SxS area to System32.
This method does not work since VC8.0.
I recommend that you refer to this article for properly deploy your DLLs:
Visual C++ Libraries DLL Deployment
http://blogs.msdn.com/aymans/archive/2006/04/04/568466.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================================