LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Old .NET reference doesnt go away from Labview

Sorry to hear that you are still having trouble. Let's try this to narrow down the problem.

1. Run FUSLOGVW.exe
2. Click Delete All
3. Make sure "Log Failures" is set.
4. Make sure "Default" is selected.

Now load LV and your application. Wait a bit - this will help with the timestamps in the log. About 30sec - 1min should be fine.

Now run the application.

Once you clear the exception and stop the application, hit Refresh on the Log Viewer.

Unfortunately the viewer is a bit primative so you will need to send me the screen shots of the main view as well as the text for the various failures.

To get the failures, double click on each failure line. That should launch your browser and display the log error. Cut-n-paste that text and send it to me. Go ahead and email it to bloggingbrian@gmail.com. I'll post back to the thread with what I find.
0 Kudos
Message 11 of 12
(1,441 Views)
Just to let everyone know what we have discovered. I should have caught it in the original posting but I failed...sigh...

The problem is that the assembly he is using is digitially signed (see the non-null public token value). This makes it a strongly named assembly and therefore follows the .NET rules for such things. By that I mean that Fusion will load the version supplied to it and no other, regardless of whether it is in the GAC or not. The only way to redirect Fusion is through the version policy files.
0 Kudos
Message 12 of 12
(949 Views)