Search results

...ategory:OPC compliance]] [[Category:Visual Studio 2012]] [[Category:Visual Studio 2013]] [[Category:What's New]] * Visual Studio 2012/2013 are now the targeted development tools with QuickOPC.NET.

== OPC Studio 2024.1 - == ...nguished from the previous one by product restructuring - now we have "OPC Studio" product family, with QuickOPC and Excel Connector as member products.

* Windows Server 2012 R2 (x64) is no longer supported. ...nsequence of the workaround, the VS extension now requires at least Visual Studio 17.6.3.

...] [[Category:COM]] [[Category:Example]] [[Category:Visual C++]] [[Category:Visual C++ 6.0]] ...l C++ 6.0. QuickOPC exposes its API via COM, and that can be consumed from Visual C++ 6.0 well.

* Built with Visual Studio 2012 Update 1. * QuickOPC-UA components are automatically installed into the Visual Studio toolbox.

...y:Windows 8.1]] [[Category:Windows Server 2003]] [[Category:Windows Server 2012]] [[Category:Windows XP]] * Visual Studio integration: there is now an editor for UserIdentity that can be invoked fr

...ory:Visual Studio 2012]] [[Category:Visual Studio 2013]] [[Category:Visual Studio 2015]] [[Category:What's New]] ....NET Framework 4.5.2 and .NET Framework 4.6 come preinstalled with Visual Studio 2015.

...esides Visual Studio 2017, .NET Core CLI tools, JetBrains Rider and Visual Studio Code (with C# extension) are among the intended primary development tools. * Development tools: Visual Studio 2012 removed from the list of primary development tools. It will likely still wo