.net assembly loads with 7.1. doesn't with 9.0f3

[instrumento]

Maybe I'm reading that page wrong, but I just copied the seven .net dll assemblies I have into the LabVIEW 2009 (9.01) directory, created an empty vi there, added a .net constructor to that vi, and still it doesn't work, i.e. get the can't load error all along.  So I don't think this is a locating the assembly problem, unless I'm overlooking something.

[Manooch_H]

There does seem to be an issue when upgrading VIs with .NET constructor nodes from LabVIEW 7.1 to LabVIEW 2009. However, it seems that you should simply be able to double-click the constructor node and re-select the constructor, or re-create the constructor node. If this doesn't work, then I would still lean towards this being a problem with locating the dependency assemblies. Have you tried creating a LabVIEW project as the KnowledgeBase article suggests?

Have you tried to use Dependency Walker to see if there are any dependencies it flags as missing?

[instrumento]

I don't think Dependency Walker understands/follows .NET assemblies, and indeed just downloaded the latest version and they don't show up.  And, by the way, the only "regular" DLLs missing from the assembly I'm trying to construct a .NET object with are IESHIMS.DLL and WER.DLL, but those are IE8 things needed on VISTA/Windows7 and not on XP where I am.   So unless LabVIEW 2009 wants me to hunt down these files, which don't apply to XP and add them to the system, this is probably not the case.  I search on Microsoft and they don't offer them and I'm not about to copy a Vista/Win7 DLL into my system.

Double-clicking the constructor node and re-selecting the constructor is how I ran into this problem!!  I can't see/connect to the constructor as LabVIEW spits out "an error occurred trying to load the assembly".  I can't reconnect to something LabVIEW doesn't show me.

Not sure how a project would help.  I've got all my .NET assemblies in one folder and just tried creating a project, adding all the assemblies to it, saving it, reopening it, creating an empty VI with a disconnected .NET constructor. Saved everything again, opened the vi, tried to reconnect to the constructor and get the same error.

I'm trying to rebuild the Assemblies myself, though I'm not sure I can get back the same exact assembly as before (everything is under source control, except the assemblies themselves, so replicating the state of the depot to get it is going to be interesting.)

[Manooch_H]

Apologies for my oversight regarding Dependency Walker. You could view the dependencies using .NET Reflector, which from your previous posts it sounds like you have already done.

Are you working with an applications engineer in this matter? At this point it might be more beneficial for us to get your test files and investigate this issue on our end.

[instrumento]

Request number 7285063.   The .NET assemblies are not mine, though I have access to the source, so I need clearance to send them in.