AnsweredAssumed Answered

Run .NET 4 assemblies in VEE 9.32 ?

Question asked by theonlyhenni on May 17, 2016
Latest reply on Jun 22, 2016 by ScottS

Like • Show 0 Likes0
Comment • 3

On a Windows 2008 R2 server (with installed .NET 4, IO Lib Suite 17.2 and VEE Pro 9.32) I try to work with a sample dll compiled for .NET 4.

When I try to import my library via menu option Device -> .NET Assembly References -> Browse, I get the following error message box: VEE can't register the ActiveX control, please run VEE as administrator. .

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.

How can I narrow the problem down ? What could be the reason ?

No one else has this question

Outcomes

theonlyhenni May 17, 2016 5:50 AM

I've found another thread with a solution that works to me:

https://community.keysight.com/thread/21609?q=Run%20.NET%204%20in%20VEE%209.32

Is this the official (supported) solution ? What about .NET 4.5/4.6 ?

Actions

dBdetlef @ theonlyhenni on May 20, 2016 5:37 AM

This is not an officially supported solution, but it helps you ;-)

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.

Actions

ScottS Jun 22, 2016 6:52 AM

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.

Actions

3 Replies

theonlyhenni May 17, 2016 5:50 AM
Mark Correct
Correct Answer
I've found another thread with a solution that works to me:
https://community.keysight.com/thread/21609?q=Run%20.NET%204%20in%20VEE%209.32

Is this the official (supported) solution ? What about .NET 4.5/4.6 ?
Like • Show 0 Likes0
Actions
- dBdetlef @ theonlyhenni on May 20, 2016 5:37 AM
  Mark Correct
  Correct Answer
  This is not an officially supported solution, but it helps you ;-)
  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.
  Like • Show 0 Likes0
  Actions
ScottS Jun 22, 2016 6:52 AM
Mark Correct
Correct Answer
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.
Like • Show 0 Likes0
Actions

Run .NET 4 assemblies in VEE 9.32 ?

Outcomes

Related Content

Recommended Content