ModelSupport transition to .NET

[kent.wedeking]

In case its not obvious, I'm creating a new process model instance for our new (better?) test executive.  ModelSupport (or rather ModelSupport2) is still in NI LabWindows/CVI?  Are we ever going to see a version of this assembly that is NOT compiled in CVI?

If case you are wondering why, my only reason why is "Last I knew CVI was going away slowly but surely".  

My other why is "I'm already developing in TestStand and in .NET.  Why would I want another language?"

[santo_13]

---

@kent.wedeking wrote:

In case its not obvious, I'm creating a new process model instance for our new (better?) test executive.  ModelSupport (or rather ModelSupport2) is still in NI LabWindows/CVI?  Are we ever going to see a version of this assembly that is NOT compiled in CVI?

If case you are wondering why, my only reason why is "Last I knew CVI was going away slowly but surely".  

My other why is "I'm already developing in TestStand and in .NET.  Why would I want another language?"

---

I guess since it is still working, why refactor or migrate to a new tech stack?

[RonghuaWang]

looking forward the .net version 

[kent.wedeking]

You know, I assume they’ve already done this for TestStand to run on Linux.

also I need to extend model support.  I have development going on already developing new packages and assemblies in .NET for my next evolution of my executive.  I would like to remove and IDE if I can.  Also I want to utilize a modern CI/CD pipeline.  CVI makes that more difficult.