.dll, other install programs

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm trying to use 3 .net C++ built dlls in a National Instruments LabWindows
application and include them in the LabWindows (5.5) install. I've installed
the .net 1.1 framework on the target computer, but when I run my application
after the install, I get a "application did not initialize properly
(0xc0000005)" error. This is occuring on a Windows XP machine, sp2. My
application runs fine on the Windows 2000 machines I've installed it on and
the older versions of my app that use a Visual C++ 6.0 built dll run fine on
the XP machine. What is going on? Do I need to do something special in the
registry or something for the .net built dlls under Windows XP? Thanks!

I've also posted this under .net-general discussion since I didn't know
really which was more appropriate...sorry about the double-posting
 
On the C: drive.... I've tried it on a second XP machine that is on a
partition labeled G: as well.

I've done more investigation today too, and it is very, very odd. I took
the LabWindows app an removed the .lib file and commented out the 6 calls to
the dlls and re-compiled it. That version runs fine on the XP machine.
Additionally, I created a hello world app in .Net, pointed the project debug
settings to my LabWindows app and ran in in the debugger. The version
without the .net dlls loads all the LabWindows DLLs, my non .net dll and then
executes the app. The version with the .net dlls loads all the dlls
(including the 3 .net dlls) without a problem, but then it throws an
"unspecified non-handled exception" and exits. Even more odd, we took the
test app for the dlls and it runs fine on XP. We then took our hello world
app and had it call the DLLs in the same way that the LabWindows app was
(through some pinvoke and other stuff...didn't quite follow it b/c I was off
on other stuff for part of the time.) That app also called the DLLs without
incident. Finally, we took my LabWindows app and put a printf statement as
the first thing in Main(). That printf line is not even being displayed, so
whatever is messing us up occurs even before we can make any sort of calls to
the dlls.

Any ideas on this, please, please let me know! Thanks! :)

Scott
 
Back
Top