This chapter describes the steps necessary to

• upgrade an existing OPC DA application with OPC UA capability
  
• create a new OPC DA / UA client application

OPCDA.NET-UA based applications can access OPC DA and OPC UA servers, even concurrently.
What server is accessed is determined by the server identifier;

• for OPC UA servers the server identifier has the format:       UA:url
  e.g.   ua:localhost/xiOPC
  See below for a detailed description of the url format.
  
• For OPC DA server the identifier is a DCOM ProgId
  e.g. Advosol.SimDAServer.1
  The ProgId identifier is exactly as it used to be. The restriction is that is must not start with "UA:"

UA Server URL format

OPCDA.NET-UA based applications work with OPC DA and UA servers. The server accessed depends on the server identifier string.
For UA server access the identifier has to have the format:     UA:url
otherwise it's used as an OPC DA ProgId for the access to an OPC DA DCOM server.

The UA server URL  has the format:   scheme://host:port/name
e.g.   http://localhost:80/Advosol/uaSim
         opc.tcp://localhost:62849/Advosol/uaSim

OPCDA.NET-UA will try to select an endpoint with the specified scheme. If no such endpoint is available then one of the available endpoints is used.