Cannot build my application after updating an assembly version number.

[J._Mondry]

Hello Benjamin,

please find attached a labview view that references the .NET assembly czframework.dll 1.3.0.0 and warns about path changes.

We cannot get it to build.

Please put the assembly into your GAC first. It is stong named.

By the way, I'm not Jens Mondry, but his collegue who cares about the .NET to LabVIEW interop issues.

Thanks!

[Ben_...]

Hello,

i put the assembly into the GAC, but i could not use this assembly in LabVIEW (8.2.1 and 8.5) i get an error (see attachment)
Do you get the same error or is this a problem on my system ?

Regards

Benjamin

[J._Mondry]

Hello,

sorry for the incomplete files.

please find attached the archive containing another assembly that is being referenced.
Please put both files into the GAC before accessing czframework.dll via labview.

Thanks for your enduring effort!

Sebastian

[Ben_...]

He Sebastian,

I could use your assembly within LabVIEW 8.5, but I do not have used the previous version of your assembly.
But i build a simple strong name assembly add it to global assembly cache with the Microsoft .NET Framework Configuration Tool (click Start, click Control Panel, click Performance and Maintenance, and click Administrative Tools. In the Administrative Tools window, double-click Microsoft .NET Framework Configuration) and use the assembly (Version 1.0.0.0) within LabVIEW 8.5 build a Application.
I rebuild the assembly with a new version number (Version 1.0.0.2) install it into the gac then start the VI with the assembly, LabVIEW ask if i want to use assembly (Version 1.0.0.2) in place of the assembly (Version 1.0.0.0). I build the application and it run no error.
Could you please check if the error also occur if you do it in similarly way or if you use the attached assembly

Best Regards
Benjamin

[J._Mondry]

Hi Benjamin,

I've tried to reproduce this behaviour. It worked on my computer too, however i was able to monitor, that labview actually called the 1.000 intead of 1.001 despite 1.001 was displayed as the selected assembly.
The only way to get around that was to remove the 1.000  assembly from the GAC and then reopen the vi and rebuild it.
After that problem we get the error. Have you been able to check our assemblies?
Are you able to build the example that is attached to this thread?

thanks in advance for your enduring effort!

Sebastian

[Ben_...]

Hi Sebastian,

yes, i build the example that you have attached and get no error.
Could you build any other application with a assembly?

Best Regards
Benjamin

[J._Mondry]

Hi Benjamin,

Yes, we use this assembly widely and were also able build a new vi with that file and compile an executable.
Only when we have the version update scenario, the vi fails to get compiled as an executable.

Strange LabVIEW stuff. I wonder how many years they will need in order to get the versioning issue solved smoothely.


Any more Ideas?

Thanks, Sebastian