03-16-2010 12:46 PM
Hello,
After starting an exe I get the attached message. I'm using 8.6. The exe is rather large ~12 MB. I'm not sure what other info would be useful
TIA,
Bill F
03-16-2010 12:50 PM
03-16-2010 12:51 PM
Hi Bill,
can you give some more information? Are there some dynamically loaded vi's in your application. Is there a dll missing? I never had problems because of the size of an executable, so i think this shouldn't be the reason for this message.
Mike
03-16-2010 01:00 PM
Wow, world record for fast responses.
The program runs fine in the IDE, so I don't think it is related to missing dlls or drivers not installed. Would'nt I have broken vis if they can't find a dll?
No installer yet. I'm running from my dev machine where it is compiled
There are a few vis that are loaded dynamically. They are included in the build as such. This error comes up as soon as the program starts, before any dynamic vis would be loaded anyway.
I'm using a wide variety of hardware, and the drivers are loaded on my dev machine, where I am compiling
The weirdness of the error message makes me think this isn't due to one of the usual suspects. anybody seen this message before?
Bill F
03-16-2010 01:22 PM
03-16-2010 01:25 PM
03-16-2010 02:14 PM
Mishkin,
I have several versions of .NET installed - the latest is 3.5 SP 1
Dennis,
OK, but if the dll is found while running in the IDE, does that mean the builder is simply failing to copy it to the data directory? I have 3 LV dlls in there now: lvanalys, lvalarms, and lvuste, along with dlls from OEMs. There is one dll missing - for a 1553 card. We have used these cards before and the dll is copied to the data directory during a compile, I'm not sure why it is not now. I copied it to the data directory and the error was still there when the exe is started(?)
Also, the builder is creating directories for vis from the NI Report Generation Toolkit. My understanding was that this was because unused vis from classes are included in the build. My app is almost 100% class-based, and there are vis that are not used in the app, yet they do not show up in directories after the build. Should they be?
Bill F
03-16-2010 04:15 PM
03-16-2010 04:32 PM
Thanks for the help. I started giong back and undiong any recent changes to see what would happen. When I disabled the code in the attach - the problem went away. After a few successful compiles, I reenabled the code and the problem did not return. LV - heal thyself!
I will be doing frequent compiles for the duration of this project...
Bill F