This is followed by a subsequent error message box stating: "mydll.dll" is not a valid .NET assembly or COM type library file.

My library consists of a simple public class with a couple of static methods (to try different parameter types). With a test program, it works, so it does not look like a general .NET problem. Further, compiling it against .NET 3.5 works fine without problems.

The newer versions can be implemented in similar way, if you have a look in the config file and the differences there.

Vee was developed ( 9.32) before Dotnet 4 and so on was on the market.

Regarding some info from keysight, there will be an update in about 2017 with full support of WIn10, that means also newest dotnet versions. As Win 10 is always changing and not final, you may imagine that exact timing is hard to get.

So, give it a try, but dont blame keysight if it is not working properly as not officialy supported.

I have tried the "hack" mentioned to the config file and it does work. It only worked (for me) in the full Vee. Doing the same thing in the vee runtime did not work. I also noticed that if you make this edit, and add some new net stuff to your program, then build a .vxe, it does not work.