Thanks for the reply but I'm a bit disappointed and confused.
I manage a test software platform which uses a custom UI built on the simple UI example (\TestStand 2023\UserInterfaces\Simple\CSharp) provided with TestStand. That UI example is based on .NET Framework 4.8 - and this is still true for TestStand 2024.
My UI has migrated easily enough - since there are basically no differences in the simple UI example between TS 2019 and 2024. But it puts me in the position where my platform is forced to contain both .NET8 assemblies (for the TS-callable components called by my process model and utility functions callable by test programs built on my framework) and .NET Framework 4.8 for the user interface. This in turn causes platform incompatibilities between my UI code and other support modules.
I'm trying to figure out how to work around this incompatibility (some form of a remote-procedure-call library built in .NET Standard) - but haven't achieved it yet and not 100% sure it's achievable or worth doing.
Based on your response, it looks like I'll probably stay on TS 2023 until a new TestStand UI model is deployed which gets rid of ActiveX and moves away from .NET Framework. The published roadmap says that's in development for 2025+. Can you provide any insight on how far out the "+" might be?
I'm also curious to know more about the performance trade-offs you mentioned - is this just related to the differences between the .NET frameworks or is there more to it? I think a very large portion of your C# user base (100% of which until now has been on .NET Framework) is going to run into this same migration wall. Microsoft hasn't announced any end of support for .NET Framework on Windows - only that they're not continuing to develop it. Seems like a mistake to just drop support for it.
Thanks again for the discussion.
