VS2010 crashes with BSOD when target Framework is changed

[Justin_E]

All,

One possible workaround for this BSOD issue is to target .NET Framework 4.0 in your application w/ DAQmx 9.2.3 installed, as Brad alluded to. Please try downloading this driver and changing your project to target .NET Framework 4.0, and let us know if this does not resolve your issue. Again, this is only a temporary workaround until we can fix the underlying issue.

[ralfeden]

Dear Justin,

where can I find the DAQ-mx 9.2.3. I can't find it in the download zone for the drivers, and also not on your ftp server.

Regards,

Ralf

[Justin_E]

DAQmx 9.2.3 is currently included with the November 2011 Device Driver distribution

[Justin_E]

Hi everyone,

I'll also work on getting the DAQmx 9.2.3 distribution up on our public FTP for download temporarily. If your project requires you to target .NET Framework 3.5, then here's another possible workaround for this issue:

Add the following somewhere within the <Project> tag in your .csproj file:

  <PropertyGroup>
    <TrackFileAccess>false</TrackFileAccess>
  </PropertyGroup>

Note that this workaround disables the incremental build capability within Visual Studio.

If anyone attempts either of these workarounds (upgrading to DAQmx 9.2.3 or adding this tag), please post back here letting us know whether or not this has resolved the issue on your machine.

[Grant_LECO]

I had my project in CVS so every time files were removed erroneously I could just load them back. Using 9.2.3 of NiDaqmx and building against 4.0 of the .NET framework fixed everything for me. I've been developing for a couple of days now without any issues

[Justin_E]

All,

I've placed the DAQmx 9.2.3 distribution on our public FTP temporarily, if you'd like to try this version as a workaround:

ftp://ftp.ni.com/support/daq/support/NIDAQ923f1.exe

[Alias312]

Not sure if this new huge installer will help or not but we cannot such a large file in our software VS installer. Is there a smaller file? I cannot believe we need to run this monster to make one small card to work!

[Justin_E]

Hi Alias,

Both options I've given are only workarounds until we determine and resolve the issue in our NI-PAL driver. They're not intended as a final fix for this issue, just something you can try to get things working while we investigate into this further. If you can target .NET 3.5 in your project, you can use the other workaround I've posted above which does not involve installing DAQmx 9.2.3.

[Mitch7]

Glad to see the 9.2.3 release of NI-DAQmx that fixes this problem and supports .Net 4.0. However, the installer at

http://joule.ni.com/nidu/cds/view/p/id/2260/lang/en

is 1175 MB. For 9.2.2 you had a similar large installer, and a smaller installer that was only 154 MB. It was called "NI-DAQmx Run-Time Engine 9.2.2" and is located here:

http://joule.ni.com/nidu/cds/view/p/id/2216/lang/en

Since we repackage the NI installer in our installer, we need to use the smaller installer. When will this "run time" version of the 9.2.3 installer be available?

Thanks,

Mitch

[sww]

Hello Justin,

I'm afraid that the latest drivers didn't solve the issue for us. Still sometimes our files are deleted. I've attached some images in which you can see that the files are gone after NI dll's were loaded.

Sjoerd