N/APosted on - 04/15/2014
We are working on an OPC Project and have .Net Assemlys in dlls from a vendor. The vendor provides 3 assembly dlls for .Net 1.1, 2.0 and 3.5. When I try to browse to a constructor on the .Net 2.0 dll I get an an error "The selected file is not a .NET assembly, type library or automation executable."
The selected file is not a .NET assembly, type library or automation executable.
Selected file is not a .NET assembly, type library or automation executable.
This problem was not actually caused by Microsoft Windows or by the operating system itself where it can’t understand the file you selected. It is actually caused by the application you used, in case you are using LabVIEW for this task. This issue is caused by the file “labview.exe.config” located in “C:Program FilesNational InstrumentsLabVIEW 8.x”.
Though I’m not sure what the file is really meant for, but it pushes LabVIEW to use a certain version of Microsoft .NET Framework, in your case maybe it’s Microsoft .NET Framework 1.1. That’s why when you want to build using Microsoft .NET Framework 2.0, the file forces LabVIEW to still use Microsoft .NET Framework 1.1 which will result for the file to be unrecognizable or somewhat invalid.
The solution to this is to simply delete the file. Open Windows Explorer and go to “C:Program FilesNational InstrumentsLabVIEW 8.x” and find “labview.exe.config”. Delete the file and you can now work normally on the DLL files.