彩票走势图

Advosol提供的软件组件和工具使得OPC与.NET的整合非常简单：

• .Net OPC客户端

　　该客户端开发组件允许.Net客户端应用程序访问OPC服务器。这些软件包要比.Net包装器简单的多。它们为高效率的应用程序开发提供所需要的一切。所有的OPC定义的功能可以通过一个数据正确转换后的类来轻松访问，附加的软件层提供了一些更高层次的功能，如在一个.Net树形结构中浏览服务器支持的项。Visual Studio项目和类生成向导使得使用起来简单快捷。在Visual Studio整合的帮助提供上下文相关的帮助。

• .Net OPC服务器

 　　.NET服务器工具箱拥有一个与通用的COM服务器和一个.NET包装器相兼容的OPC标准，它允许应用程序指定服务器需要通过VB.Net/C#以一个程序集的方式实现的功能。

现在，怎样开发OPC DA服务器？

　　现在如果您需要开发一个新的OPC服务器，那么您需要制定一个基本的决定：是否当前的开发需要在传统的DCOM技术或当前的.NET和XMLWeb服务的基础上完成呢？

　　Advosol提供的这些组件实际上阻止了这些不得不做出这样的决定。你可以使用Visual Basic 或C#来开发一个OPC服务器作为一个.Net程序集，并且以一个OPC DA或XMLDA服务器来运行它。

　　由于它在OPC服务器中是一个通用的工具箱，Advosol服务器工具箱在一个通用的服务器部分实现了OPC特定功能并且用户只需要提供与设备访问的功能的一个.Net程序集。 该.Net程序集不需要任何COM功能，它是多线程的并且没有基于ActiveX解决方案的局限性。

现在，怎样开发OPC DA客户端？

　　OPC的DCOM基础框架已被宣布为传统技术，现在微软新的开发基础框架是.Net和web服务。OPC客户端应用程序的开发人员如此快速地遵循这一趋势，而且新的OPC客户端可能被开发为.Net应用程序。然而目前已安装的设备中，大多数拥有的是基于DCOM的OPC DA V2的服务器。需要远程访问的设备可能拥有基于web服务技术的OPC XM-DA服务器。这就意味着目前这些客户端大多数访问OPC-DA服务器，不久将可能访问XML-DA服务器。

Advosol offers software components and tools that makes the combination of OPC and .NET real simple：

• .Net OPC Clients

The client development components allow .Net client applications to access OPC servers. These software packages are much more than simple .Net wrapper. They provide everything needed for efficient application development. All OPC defined functions can be called through easy to use classes with all data properly converted. Additional software layers offer a number of higher level functions like browsing the server supported items into a .Net TreeNode structure. Visual Studio project and class generation wizards make usage simple and quick. The Visual Studio integrated help offers context sensitive help.

• .Net OPC Servers

The .NET server toolkits have an OPC standard compliant generic COM server and a .NET wrapper that allows the application specific server functionaly to be implemented with VB.Net/C# as a .NET assembly.
 

How to develop OPC DA Servers today?

If you have to develop a new OPC server today then you have to make a basic decision: Should the development be done on the legacy DCOM technology or the current .NET and XML Web Services base?

Advosol offers components that actually prevent having to make such a decision. You can develop an OPC server as a .Net assembly using Visual Basic or C# and run it as an OPC DA or XML DA server.

As it is common in OPC server toolkits, the Advosol server toolkits implement the OPC specification in a generic server part and the user only has to supply a .Net assembly with the device access functions. This .Net assembly doesn't use any COM features, is multi-threaded and doesn't have the limitations of an ActiveX based solution.

How to develop OPC DA Clients today?

The DCOM base of OPC is declared a legacy technology and Microsoft bases new developments on .Net and web services. Developers of OPC client applications follow this trend rather quickly and new OPC clients are likely developed as .Net applications. Most devices installed today however, have DCOM based OPC DA V2 servers. Devices that need to be accessed remotely are likely to have OPC XML-DA servers based on the web services technology. This means that clients currently mostly access OPC-DA servers but will soon have to be able to access XML-DA servers.