I
_iycrd
After several frustrating attempts to wrap a native DLL w a C++/CLI
DLL, I finally got an assembly to compile, only to find a *runtime*
error. The app comes up fine. Test dialog displays. Clicking on the
button that creates the wrapper class causes an exception, not in the
button's event handler, but in Application.Run() within Main(). The
error:
! System.IO.FileNotFoundException was unhandled
Message="The specified module could not be found. (Exception from
HRESULT: 0x8007007E)"
I initially thought the message was complete nonsense, but on
researching this I found a number of similar incidents. Apparently
this relates, once again, to a manifest file.
The thread at:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130243&SiteID=1
refers to a bug report submitted to Microsoft:
http://tinyurl.com/f78bv
Unfortunately, MS closed the bug report as 'by design.' Why MS would
regard it as 'by design' is beyond me, and I can't make much sense of
their recommendation (can anyone?). Their workaround (copying/
renaming the manifest from the DLL to the C# app folder) did not work,
of course.
Does anyone have any idea what's going on here or how to get around
this?
PS: Platform is VS2005, XP Pro, 32-bit, Pentium, all standard stuff.
Someone in the thread above said "weren't these .NET languages
supposed to be compatible?"
DLL, I finally got an assembly to compile, only to find a *runtime*
error. The app comes up fine. Test dialog displays. Clicking on the
button that creates the wrapper class causes an exception, not in the
button's event handler, but in Application.Run() within Main(). The
error:
! System.IO.FileNotFoundException was unhandled
Message="The specified module could not be found. (Exception from
HRESULT: 0x8007007E)"
I initially thought the message was complete nonsense, but on
researching this I found a number of similar incidents. Apparently
this relates, once again, to a manifest file.
The thread at:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130243&SiteID=1
refers to a bug report submitted to Microsoft:
http://tinyurl.com/f78bv
Unfortunately, MS closed the bug report as 'by design.' Why MS would
regard it as 'by design' is beyond me, and I can't make much sense of
their recommendation (can anyone?). Their workaround (copying/
renaming the manifest from the DLL to the C# app folder) did not work,
of course.
Does anyone have any idea what's going on here or how to get around
this?
PS: Platform is VS2005, XP Pro, 32-bit, Pentium, all standard stuff.
Someone in the thread above said "weren't these .NET languages
supposed to be compatible?"