04-11-2019 11:40 AM
Hello,
I am trying to select a .dll to use in a >NET constructor. I keep getting an error and i have no clue why this is happening. I have tried labVIEW 2017 both 32 and 64 bit, but i am still unable to get the vi to work, the vi will print a label and i am using Seagull.Bartender.print dll.
Any suggestions to help me get this going is greatly appreciated. As a note, I am recently starting to use labVIEW.
04-11-2019 06:39 PM
There are other posts on this forum about the same issue, you could try that nifty search function.
Possibly a CLR versioning issue. If you are running Windows 10, try to install the .NET Framework 3.5 as this is not installed by default (this will install CLR 2.0).
Another option is that the assembly is blocked. Make sure it is unblocked (check file properties) and that it is present in the same folder as your LabVIEW project (which of course you are using).
04-16-2019 03:17 PM
Hello,
Tank you for replying.
I read in the forum about forcing assemblies form CRL 2.0 with CLR 4.3.
My question is if the information provided in the file is all that is needed or there is some configuration information that must be added to the file, please see capture. I use win 7 so I guess I should not need to install .NET framework 3.5?
Regards
04-17-2019 05:49 PM
Hello avega,
It is my understanding that the code mentioned in the LabVIEW 2017 Help documentation should work. Please let us know if you are continuing to have issues after implementing the configuration file.
Best regards,
04-17-2019 06:05 PM
Hello,
Before implementing the code I would like to know if I need to add extra information to the file labVIEW.exe.config or that it should work just the way it is.
Regards.
04-18-2019 11:11 AM - edited 04-18-2019 11:12 AM
Hello avega,
The LabVIEW.exe.config file should work the way it is provided in the help documentation. No extra information or revisions required. It is my understanding the since we are using a LabVIEW 2017 (a version after 2013) and a Windows 7 computer, the configuration file the documentation describes should work.
Best regards,