Inconsistent problems with .net constructor node

[xiv014]

When I double click on the assembly node and browse to the folder I have my dll's in I periodically come across a few problems:

1 When I select a dll the wrong assembly appears (sometimes)

2 When I select a dll the correct assembly appears, but there are no longer any objects available

I see the changes sometimes after closing labview and sometimes after just closing the vi in question (to be clear this is happening on multiple vi's).

Any help would be appreciated.

Thanks

[Jarrod_S.]

Are these assemblies stored in the GAC? Could this be a versioning issue?

[Lycangeek]

Are you using LV 7.x? I know we fixed some problems where the name parser became confused and you could see these sorts of issues. But if you are seeing it in 8 also, that is new.

[xiv014]

Thanks to both of you for the quick response.  I am using Labview 7.0, but what is the name parser?  Since my original post I have placed the most recent assembly in c:\windows\assembly, updated the .net assembly reference in Labview and deleted all other versions of this assembly from my machine.  I started going through every constructor node in every vi that referenced the old assembly and manually updating them.  This worked great for the first five vi's or so, but on the sixth vi all of the constructors under the object I've been working with are no longer visible.  I have since gone back into the five vi's I updated manually and the constructors I had been seeing are no longer available.  I've tried restarting Labview and my Windows, but so far nothing has worked.

Any feedback would be great.

Thanks

[Lycangeek]

The name parser is the code we use internally for getting the information about the .NET types into LV. LV 7 was the first version to support .NET and there have been a lot of improvements since then, especially with LV 8.

When you say you put the assembly into c:\windows\assembly, do you mean you just copied it to that directory, or used gacutil or the .NET Wizard to install the assembly into the GAC? the \windows\assembly directory is actually a kind of "special" directory that you should only access through tools. To be able to put the assembly there, you need to digitally sign the assembly (sn.exe, in the .NET SDK or VS.NET) and then use the above tools to install it into the GAC.

Also, when you say you've been going back and updating the constructors, etc., what do you mean? Updating to what?