.NET Assembly Manifest Changed

[telos]

I have got a problem with the .NET support in Labview 7 Express. I have written some VIs, which implement Labview wrappers for a .NET assembly written by our company.

Due to a new release of this assembly, the version number of the assembly (in the manifest) has changed.

How can I tell my Labview VIs to use this new version of my assembly (the assembly has got the same filename and the methods/classes have not changed).

I have deleted all copies of the old assembly created by Labview and I have added the new assembly to the ".NET Assembly References" dialog. But Labview does not find the new assembly. Why?

[bilalD]

Hello

LabVIEW will not be able to automatically update its references to point to the newer version of the dll. This is something you will have to do manually. Try going to the refernce that you created for the dll for the older manifest and changing it to the new one. Right click on the constructor node and target it for the newer dll.

I hope this helps

Bilal Durrani
NI

[pcbv]

I have the same problem with the new release of the assembly.

The problem is that we are in a period of developing our software. For this reason we have each weak a new release of the assembly. In the same time, we develop the applications in LabVIEW. If I must change manually the update for new assembly every time will be a very big problem.

The bigger problem is that I must construct the sub vi and when I update the assembly, even if I update manually the constructor, the references from sub vi don’t update automatically. We will have approximately 100 sub vi. For this reason we must find an automatically way to update the assembly.

Is there someone who knows how to do this?

Petru COTFAS

[AnalogKid2DigitalMan]

Related discussion in parallel ongoing here:

http://forums.ni.com/ni/board/message?board.id=170&message.id=142640&page=1