Can't load .NET properly in window 10 for labview 2014 and later

[Tphan]

I am having a problem that is seem to be no answer or properly answer to the issue.:

I have a .NET dll that is called by Labview.  This have no problem what so ever in window 7.

  How ever since I switch to Window 10 I encounter several problem.

1./ The NET dll can be loaded and run properly in any Labview  version from 2014 to 2019.  But it must included in a project.

2./ The .Net can not be loaded and get an error when run a stand alone vi that  called directly the dll without putting the VI in a Labview project.

3./  When build the executable from said project in case 1.  The executable return and error as: "The VI is not executable.  The full development version of labview is required to fix the error"

4./  Create a Labview.exe.config file to force the CL version 2 to load did not help

5./ All the Microsoft. NET version appeared to be present.

6/.  The only way is working that you have to run said Vi in a project and  building executable or installer does not work.

I hope that I get get a definite answer to the problem.  It seem to me that .Labview .NET calling function is very buggy and unstable.

  I have been trying in several Window 10 machine from fresh install to fully upgraded.  They all have the same problem.

This wasted a lot of time and my company have been using thousand off license for labview.  Hope that we don't wasted money too.

Thanks

Tphan

[tyk007]

I sense frustration. However many people have not had a problem (myself included and I do a lot of .NET integration in LabVIEW). Some tips:

• Always use a LabVIEW project for .NET integration (dev environment)
• Always include assembly dependencies in the project (unless they are in the GAC / just the framework). This helps with the next point.
• When building an executable, ensure the assemblies and dependencies are specified to be copied to the output folder

There are a lot of generic answers for what you have described - mostly because you have not given us enough detail to work with:

• What is the .NET assembly? A third-party or one you are developing yourself? The fact that your reaction differs between stand-alone VI and project implies that the assembly may have other dependencies.
• VI example with the .NET assembly attached? So we can attempt to replicate your problem.
• What .NET Framework does the .NET assembly target? You say your OS is Windows 10 - have you installed the .NET 3.5 SP1 framework (in order to get CLR 2.0)?

[Tphan]

Here is everything I tried.  zip it up it kind of big.  3 thing I do:

-Load .Net in stand alone: error.

-Load net in a vi From a project: Works

-Build executable fro project: failed to run and broken vi.

  Note that I have evry thing work fine in window 7.  Just when my company switches to Win 10 the everything fail.

The DLL has been use in many other application for C++, Tickle, C$ and many other languages.  They all work fine in Win 10.

  except Labview

THanks

Tphan

[Tphan]

Here it is the Files

Please see to your heart content.

Tphan