OPC Studio User's Guide and Reference
Transitioning from .NET Framework to .NET 6+
If you have previously developed with QuickOPC for .NET Framework and are now transitioning to .NET 6+, you may continue to use your existing code, as there are practically no coding differences between the two. There are, however, differences in other aspects, such as the supported functionality, tooling, installation, security, user interface, deployment, use of examples, etc.
For easier transition, we recommend that you read the following articles, which cover the areas that specifically need your attention.
|
In runtime, all user interface features (such as controls, dialogs, and live binding; Windows Forms and WPF) and non-visual components are supported both under .NET Framework and .NET 6+. However, "designing" them (this includes tasks like dragging from the Toolbox, or configuring in Properties window) in Visual Studio is only possible in .NET Framework projects. In order to achieve visual design for .NET 6+ projects, the developer can make two project files over the same set of source files, one targeting .NET Framework and one targeting .NET 6+, and use the project that targets .NET Framework for visual design tasks. |