.net versions Labview

[JerReilly]

I built a .NET assembly in C# and then built a large number of LabView VI's that use that .NET assembly.  I have found in the past that whenever I make any significant change to my .NET assembly I have to then go back and rework a large number of my VI's even though none of the .NET interfaces have changed.  While that is annoying and tedious I figured it out a while ago and can deal with it.

Now I have a new but related problem.  I just made more changes to my .NET asembly and gave it a new version number.  I then went back and reworked all of the VI's using LabView 8.0.  That all worked fine and everything runs correctly under LabView 8.0.   I then took the new .NET assembly and VI's and tried to run them on Labview 8.5.  When I load any of the VI's, LV 8.5 gives me many many warning messages like this "xxxx.vi Expected Assembly MyAssembly Version 1.0.2.4   ..... but found Version 1.1.0.0".  The VI's do run correctly and do pick up the new .NET version but the warning messages are really confusing and annoying to our customers.

I opened one of the offending VI's in a text editor and I can see that the old version number is embedded many times within the VI.   I can't figure out any way to update the VI's to just use the new version number.   In a typical case I might find 15 or 20 references to the old version number.  I've tried opening the VI in LabView and doing various edits that I think might help like delete all the .NET constructors and then rec-create them, etc.   By doing this I can reduce the number of embedded old version numbers but I can never seem to get rid of them completely unless I re-create the entire VI from scratch.

I've even tried a search/replace using a text editor to replace the old version with the new version but that causes (unsurprisingly) all kinds of other problems.

Does anyone of any ideas?

--- Jerry Reilly

--- Software Eng

--- Data Translation

[tst]

Is your assembly registered in the GAC? I have seen some people mention they had similar problems. I couldn't find anything exactly similar in a quick search, but here and here are a couple of examples. You might something more similar if you search some more.

You might note that in the second thread Travis suggested waiting for a couple of months. Since those couple of months have passed, it would be reasonable to guess that if it is the same problem, you now have to wait even less for a resolution.

[JerReilly]

Thanks for the tips.  I did search the archives but managed to miss those (very helpful) threads that you sent.  It does sound like I'm having variations of the same problems that were resported in those threads.

Yes, my assembly is in the GAC.

Since my original post I then tried to load the problem VI's in 8.5, ignore the warnings and then save from there in 8.0 format.   That caused some other issues.  It got rid of the original warnings and generated new warnings about the assemblies expected in "" but found in "NULL" which is more like what was reported in the threads you sent.

It sounds like some basic LabView infrastructure for .NET changed in 8.5.  Until that's fixed it sounds like we don't have much of an option other than telling our customers to ignore all the warning messages.

Thanks for you help.

--- Jerry