Well, the logs look fine except that I would expect to see one, such as
*** Assembly Binder Log Entry (1/31/2007 @ 2:58:35 PM) ***
The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.
Assembly manager loaded from: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: User = xxx
LOG: Where-ref bind. Location = C:\Program Files\National Instruments\LabVIEW 8.2\resource\NationalInstruments.LabVIEW.dll
LOG: Appbase = file:///C:/Program Files/National Instruments/LabVIEW 8.2/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : (Unknown).
===
LOG: This bind starts in LoadFrom load context.
WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
LOG: No application configuration file found.
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Attempting download of new URL file:///C:/Program Files/National Instruments/LabVIEW 8.2/resource/NationalInstruments.LabVIEW.dll.
LOG: Assembly download was successful. Attempting setup of file: C:\Program Files\National Instruments\LabVIEW 8.2\resource\NationalInstruments.LabVIEW.dll
LOG: Entering run-from-source setup phase.
LOG: Assembly Name is: NationalInstruments.LabVIEW, Version=8.10.11.20491, Culture=neutral, PublicKeyToken=null
LOG: Re-apply policy for where-ref bind.
LOG: Binding succeeds. Returns assembly from C:\Program Files\National Instruments\LabVIEW 8.2\resource\NationalInstruments.LabVIEW.dll.
LOG: Assembly is loaded in LoadFrom load context.
This is the successful loading of the NationalInstruments.LabVIEW.dll assembly via the LoadFrom command. Then you should also see on such as
*** Assembly Binder Log Entry (1/31/2007 @ 3:02:53 PM) ***
The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.
Assembly manager loaded from: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: User = xxx
LOG: Where-ref bind. Location = C:\Program Files\National Instruments\LabVIEW 8.2\examples\comm\dotnet\Calculator.dll
LOG: Appbase = file:///C:/Program Files/National Instruments/LabVIEW 8.2/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : (Unknown).
===
LOG: This is an inspection only bind.
LOG: No application configuration file found.
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Attempting download of new URL file:///C:/Program Files/National Instruments/LabVIEW 8.2/examples/comm/dotnet/Calculator.dll.
LOG: Assembly download was successful. Attempting setup of file: C:\Program Files\National Instruments\LabVIEW 8.2\examples\comm\dotnet\Calculator.dll
LOG: Entering run-from-source setup phase.
LOG: Assembly Name is: Calculator, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
LOG: Binding succeeds. Returns assembly from C:\Program Files\National Instruments\LabVIEW 8.2\examples\comm\dotnet\Calculator.dll.
For the calculator assembly itself. Then, if you run the VI, you should see a similar sequence, except that DNCInterface.dll should not be loaded again.
So, you keep talking about running the VI. Let's start with the basics. Can you open a blank VI, drag and drop a .NET constructor and get the assembly list to show up, or do you get the error message?
