There are a few simple steps to insure your OPC Web Alarm application is deployed properly.
You can distribute the OPC Web Alarm.NET component with your local and remote applications. This component will only connect to licensed OPC Systems Services.
If using Visual Studio, the following text is automatically added to Web.config when you add an OPCWebRefresh control to your application. In other development environments you need to add this text to support dynamic script generation:
<add verb="*" path="Dart.PowerWEB.LiveControls.GetResource.aspx" type="Dart.PowerWEB.LiveControls.ResourceHttpHandler,Dart.PowerWEB.LiveControls" />
This section should be placed in the configuration:system.web node in the Web.config file.
A "\Bin" subdirectory should be in your project's directory (many development environments create this automatically). For example, if the project is called OPCWebAlarmTest, you should have a directory structure with "OPCWebAlarmTest\Bin".
Check for OPCWebAlarm.dll, OPCWebControls.dll, OPCSystemsInterface.dll, and Dart.PowerWEB.LiveControls.dll in the "\Bin" directory. Your development environment may have already put a copy there when you added OPCWebControls and OPCWebAlarm as a reference.
To deploy your project follow these steps
XCOPY or FTP your application to a directory on the target server.
Create a virtual directory on the target server that refers to the application's new directory. Of course, you can always install directly to the "wwwroot" structure.
Now access the web site using IE at "http://yourservername/OPCWebAlarmTest/display.aspx".
Note: When deploying to IIS7 set the Application Pool to Classic .NET AppPool.