LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DLL loading problem in LV8.5

Hi all,

 

yeah, it's possible that installing .Net-Framework 3.5 solves your problems - never tried it. I also build a DLL in Visual Studio 2008 (C++) and copied it (with LabView-Project) to a new computer with Windows XP Home, no .NET Framework or Service Pack installed at all. I got the error you already mentioned. I simply installed the "Microsoft VIsual C++ 2008 Redistributable Package" from the microsoft website, which solved the problem:

http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&Displa...

 

Didn't need to install .NET Framework.

 

Hope this works for you too...installing this package only takes some minutes...

 

Greetings,

 

Christian


THINK G!! 😉
------------------------------------------------------------------------------------------------
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)
Message 11 of 18
(1,573 Views)
It work with LV 8.2.1, so that is not the problem.
0 Kudos
Message 12 of 18
(1,552 Views)
Message Edited by DannyC on 09-24-2008 02:15 PM
0 Kudos
Message 13 of 18
(1,538 Views)
That did not work either.  Here is the .dll
Download All
0 Kudos
Message 14 of 18
(1,534 Views)
I'm running into the same problem.  I created a DLL using Visual C++ 2008 Express on one system, ran it on LV 8.6, and it worked fine.  When I tried running it on a system without Visual C++, it gave the same message.  I tried installing the .NET framework, no change, installed the redistributable version of Visual C++, no change.  Now I'm resorting to installing the full Visual C++ package (170 MB!).  This is a huge hassle and, especially if the software needs to get installed on many targets.  Is there any way to compile a DLL using Visual C++ so that it doesn't use .NET?
0 Kudos
Message 15 of 18
(1,523 Views)

I thought it was a fault of mine, a misconfiguration of my C++-Settings, so I did not mention it..but perhaps it is helpful for somebody. I can't remember the error-message, but I know there IS an error message if you don't do the following (it's perhaps the same as you were already told at the beginning of the thread, but in another way...):

In C++, go to Project-->Properties. In the Configuration Properties, there's a point "Manifest Tool". Go to "Input and Output" and check that "Embed Manifest File" is set to true...don't really know what it does, but it embeds something called "Manifest", which is needed for execution.

 

Another point: Installing the redistributable package only installs the release-version of the runtime-DLLs, so check you build release and not debug-versions of your DLL. The debug libraries are only installed if you install Visual C++, but not with the redist nor the .NET-installer...

 

If this doesn't help either, try to open the DLL in the dependency-walker which shows the dependencies to other DLLs. If there are missing ones, this can show you which additional software you have to install.

 

Hope this solves your problem!

 

Greetings,

 

Christian

 

EDIT: @DannyC: I just downloaded your DLL and checked it with the dependency-walker...it tries to access MSVCR80D.DLL, that means the debug version of the runtime library, which is NOT installed with the redistributable package...manually-install this DLL to your project library (should work) or, the better way, build a release version of your DLL (will work 🙂 ).

Message Edited by cschneider on 09-24-2008 11:49 PM

THINK G!! 😉
------------------------------------------------------------------------------------------------
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)
0 Kudos
Message 16 of 18
(1,509 Views)

Thanks Christian!

 

The problem in my case was that the DLL was compiled in Debug mode which required additional files.  I recompiled as a Release and now the only thing that needs to be installed on the target is the (much smaller) redistrubutable version of Visual C++ Express.   It's still a small nuisance but much better than having to install the full version.

0 Kudos
Message 17 of 18
(1,474 Views)

Yes, that was my problem as well.  I am able to load the release version of the dll.

 

Thanks for all the help!

 

Danny

0 Kudos
Message 18 of 18
(1,468 Views)