08-09-2006 02:09 PM
08-21-2006 08:50 AM
Scot -
I noticed that this post has not received a response in a couple of weeks. Has this issue been resolved?
There should be no relationship whatsoever between NationalInstruments.Common.dll and the FGEN wrapper, so the problem as described is quite puzzling.
- David
08-21-2006 02:45 PM
David,
Thanks for your response (Has this issue been resolved?)
The answer is no. I just tried updating the registry by adding a pal memory config per the following post but it did not help.
http://digital.ni.com/public.nsf/websearch/440B50D1209E33E586256C4800475730?OpenDocument
I need this to work soon as it is holding up deployment of my test stand.
Any help would be appretiated.
Scot Hudson
850-251-4784
08-21-2006 04:41 PM
Scot -
I'd like to make sure I understand your problem correctly.
In your original post, you stated, "When I add the later (Common library) my Legacy Wrappers stop working.". I interpret this as meaning that you have a working project that uses the NI-FGEN .NET wrapper and when you add a reference to NationalInstruments.Common.dll, the project no longer works. If you remove the reference to NationalInstruments.Common.dll, the project starts working again. Is this correct?
Could you describe your system in more detail? Are you using C# or VB.NET? What version of the NI-FGEN driver is on your system? What version version of DAQmx is on your system? Do you have Measurement Studio installed?
My initial guess would be some kind of driver incompatibilty. Have you tried to load the NI-FGEN DLL in Dependency Walker? This will show you whether all of its dependencies can be found.
- David
09-15-2006 11:19 AM