AnsweredAssumed Answered

using .Net4.0

Question asked by andreas_h on Jan 27, 2014
Latest reply on Mar 31, 2014 by Ever

Like • Show 0 Likes0
Comment • 3

Hi

I'm using vee 9.32 running on .net4.5 framework.

I've got a library based on .net4.0 framework. Is it possible to import and use methods of .net 4.0 or .net4.5 library?

Since the application vee 9.3 is running on .net4.5 plattform, it's somehow expected, that also the assemblies could be referenced within vee programms.

In this forum I found (4 years old) :

Create own dotNet instruments driver use in VEE-.NET 4.0 W7P

Is there a roadmap, when .net4.0/4.5 assemblies will be supported by vee?
If there is no solution, I have to move the whole vee application to a pure .net4.5 project.

Regards

andreas_h

Edited by: andreas_h on Jan 29, 2014 12:31 AM

Edited by: andreas_h on Jan 29, 2014 12:44 AM

No one else has this question

Outcomes

Mike Jan 30, 2014 2:28 AM

I don't know Agilent's current stance on this but I can say that I recently used a 3rd-party library which was compiled for .NET 4.0 ( with 9.31 or 9.32 ) and I simply could not pursuade it to work properly. I can't remember the problem but I think it initialised okay but ignored any commands. As the library was open-source I recompiled it for .NET 3.5 which works fine. I have seen threads on a similar theme and AFAIR there were no success stories with 4.0 libraries.

I'm sure that later versions will be on the roadmap but Agilent are giong to be internally focussed for the next year or so as they are cast off into their new company Keysight; I wouldn't expect VEE X ( mentioned over 2 years ago ) is unlikely to emerge any time soon in my estimation.

Actions

dBdetlef Mar 26, 2014 4:52 AM

Have a look in the VRF, there was a "cheat" supplied to use dotnet4 with VEE 9.32 - but still keep in mind that not officially supported yet.
the cheat consists of some editing of the vee,config file..

Actions

Ever Mar 31, 2014 11:32 PM

I not sure whether this will workaround work. Since VEE does not officially support .NET 4.0

To try the workaround, start the VEE with target framework 4.0, follow the below steps.

1.     Close all the existing VEE application
2.     Backup the existing Vee.exe.config in VEE Install directory(Example C:\Program Files\Agilent\VEE Pro 9.3), or rename to Vee.exe.config.backup
3.     Copy the attachment Vee.exe.config to VEE Install directory.
4.     Launch the VEE software and import the .NET Assembly reference

Attachments

Vee.exe.config1.5 KB

Actions

3 Replies

Mike Jan 30, 2014 2:28 AM
Mark Correct
Correct Answer
I don't know Agilent's current stance on this but I can say that I recently used a 3rd-party library which was compiled for .NET 4.0 ( with 9.31 or 9.32 ) and I simply could not pursuade it to work properly. I can't remember the problem but I think it initialised okay but ignored any commands. As the library was open-source I recompiled it for .NET 3.5 which works fine. I have seen threads on a similar theme and AFAIR there were no success stories with 4.0 libraries.

I'm sure that later versions will be on the roadmap but Agilent are giong to be internally focussed for the next year or so as they are cast off into their new company Keysight; I wouldn't expect VEE X ( mentioned over 2 years ago ) is unlikely to emerge any time soon in my estimation.
Like • Show 0 Likes0
Actions
dBdetlef Mar 26, 2014 4:52 AM
Mark Correct
Correct Answer
Have a look in the VRF, there was a "cheat" supplied to use dotnet4 with VEE 9.32 - but still keep in mind that not officially supported yet.
the cheat consists of some editing of the vee,config file..
Like • Show 0 Likes0
Actions
Ever Mar 31, 2014 11:32 PM
Mark Correct
Correct Answer
I not sure whether this will workaround work. Since VEE does not officially support .NET 4.0

To try the workaround, start the VEE with target framework 4.0, follow the below steps.

1.     Close all the existing VEE application
2.     Backup the existing Vee.exe.config in VEE Install directory(Example C:\Program Files\Agilent\VEE Pro 9.3), or rename to Vee.exe.config.backup
3.     Copy the attachment Vee.exe.config to VEE Install directory.
4.     Launch the VEE software and import the .NET Assembly reference
Attachments
- Vee.exe.config1.5 KB
Like • Show 0 Likes0
Actions

using .Net4.0

Outcomes

Attachments

Related Content

Recommended Content