Configure LabVIEW for NET 4.0

[JÞB]

Yes you can.  All you need to do is search exhaustively through the LabVIEW help file to find this

Complete the following steps to force LabVIEW to load .NET 4.0 assemblies.

1. Install the .NET Framework 4.0 on your development machine.
2. Open a text editor and create a configuration file that contains the following text:
   
   <?xml version ="1.0"?>
   <configuration>
   <startup useLegacyV2RuntimeActivationPolicy="true">
   <supportedRuntime version="v4.0.30319"/>
   </startup>
   </configuration>
3. Save this new configuration file in the same directory as LabVIEW.exe. Name the file LabVIEW.exe.config.
4. Relaunch LabVIEW.

Then accurately follow the steps.

Then again, Tools>>Advanced has some useful tools available to the LabVIEW user

I would think that "Tools>>Advanced>>Configure .NET 4.0 support" would probably get more clicks than "Create or edit Express VI"....

It really only involves writing a file with a known name and known contents to a known location on a local disc..... that sounds like a Tool to me!

[A-T-R]

Oh yes, please!

I had a lot of trouble when trying to deploy a customer application which uses "Windows active directory" functions. Everything worked in the LV IDE, but after building the *.exe, I almost went nuts...especially because I had no idea what to do and the customer was literally standing behind me...

[JÞB]

Recent kudos are appreciated!

Time to change the status of this idea.  Implemented foundatianally in 2013!??? Or was it 2014? That had native .NET 4.0 support?

[JÞB]

8 years

I don't even know what is appropriate. Comma, period,  exclamation!

Hey, as long as you are marking all of my fulfilled "IDEAS" as completed.--- take one more gander at my suggestions on time-keepping.

 Hashtag time will be necessary in the next decade--- Arian and Dianese clocks will need stability. GMT and it's derivatives,  will not effective in scope to sxhyronize the rotation of this planet with the effects of Bose-Einstinian predicted dilutions.  (Time is relativel to acceleration)  Arian Time will be something special!

Allright!  To be honest, I have felt that a timebase purely based on a standard SI Second is sorely needed in computing.  That doesn't exist today! We have local and UTC times (LabVIEW keeps those times in UTC BUT, has failed to track the 37 leep-seconds]  hence my suggestion of "#" hashtag Time as third horology method (yes, I am an amateur horologist, please don't tell my ex wives!)

Time, does have relationship with space, "SpaceTime" is a very immutable interface.   So, even the French have abandoned silly constructions like "leap Seconds. "  Yet that leaves CIVIL Time continuity vague!  #T , or EVETENTUARY Time will rely upon the SI second in the local.

[wiebe@CARYA]

Of course now there will be patches, just to add your credits to the release notes.

For every LabVIEW version since LV12 (IIRC)... 🤣

[JÞB]

Actually, IIRC LabVIEW 2011 release notes missed a few 😉