You can tunnel using WebSocket between v9, v8, and v7, but you can only tunnel between v9 and v6.4 using a non-SSL connection. When tunneling between v9 and v6.4 you may run into a known issue with licensing that appears when the network of DataHub connections is not a simple star configuration. You can tunnel between DataHub v9 and v8, v7, and v6.4. Tunnelling between DHv9 and DHv8, DHv7 or DHv6.4 See below for more information about copying your local WebView pages and media to DataHub v9.

See this link to documentation for more details. The location of this directory will depend on which operating system you are running. If you want to make a backup of your current DataHub configuration, you can do that by copying the contents of the DataHub configuration directory. You can run OPC DataHub v6.4 and Cogent DataHub on the same system, though there may be conflicts that require you to modify your configuration. When you install DataHub v9 on a systems running OPC DataHub v6.4, then you will be asked if you want to copy the configuration from the earlier version, but it will not replace the earlier version. DataHub v9 will be installed and will use the existing configuration files from the earlier installation. When you install DataHub v9 on a system running DataHub v7 or v8 the installer will ask you to uninstall the earlier version. Installing DataHub v9 on a system running an earlier version Please see our Installation Notes for more details. Note: Cogent DataHub v9 contains new features that may not be supported by your target operating system.

Connect to AVEVA™ Historian and AVEVA™ Insight.

If you have apps that have been in this problematic state you’ll likely have to do some cleans on your build to ensure that the AppManifest is overridden correctly now. Once you’ve done that you can install the Silverlight To be clear, what I am outlining here will: enable you to have the latest Silverlight runtime while still building against the RTW of Silverlight 4.įirst, you can uninstall Silverlight 4 GDR1 SDK (you can do this via the Add/Remove Control Panel). If you find yourself in this situation and don’t want to keep manually changing the AppManifest attribute after each build and re-packaging the XAP, then you can do one thing to keep your environment the way you expect it.

Keep up-to-date on the latest developer runtime.

If you’re in the situation as described above where your users are seeing a prompt that is not expected, you can easily modify your dev environment to prevent this. I would try to get it unblocked, as it often contains valuable information.

Install older version of silverlight