Deployment

Deploying a Web application that uses the PowerWEB TextBox control for ASP.NET is easy. Visual Studio users can simply Rebuild the Project (to insert the license) on the development machine (the licensed machine), and then XCOPY or FTP the application to the server.

While developing the following steps should have already been taken.

If you are instantiating the component dynamically, be sure to include a licenses.licx file (see Creating The Licenses.licx File for more information).
If using Visual Studio, the following text is automatically added to Web.config. In other development environments you need to add this text to support PowerWEB CallbackManager Viewstate management:
```
     
<httpModules>
        <add name="CallbackManager" type="Dart.PowerWEB.TextBox.CallbackManager,Dart.PowerWEB.TextBox" />
</httpModules>
                                
```
If the Project includes other PowerWEB references, the CallbackManager from another PowerWEB product may alternatively be used.
A "\bin" subdirectory should be in your project's directory (many development environments create this automatically). For example, if the project is called LiveTest, you should have a directory structure with "LiveTest\bin".
Check for "Dart.PowerWEB.TextBox.dll" in the "\Bin" directory. Your development environment may have already put a copy there when you added TextBox as a reference.

To deploy a licensed ASP.NET Web Application or Web Service, follow these steps.

Compile the ASP.NET application on a licensed development machine.
Copy the contents of the bin folder and the ASP.NET source files (such as .aspx files) to the server that will be hosting the application.
Create a virtual directory pointing to the folder containing the Web Application or Web Service. Of course, you can always install directly to the "wwwroot" structure.

Note: It is not necessary for the deployment server to be licensed or to contain a copy of a license in its registry.

Using External Script Files

In some cases where security settings or application URL rewriting may interfere with script access (e.g. within a DotNetNuke module), you need to physically supply the script resources and/or unique security settings. In your TextBox installation directory you will find a Scripts directory. Place the contents of this directory anywhere on your web server and add the following to your application’s Web.config within the appSettings node, replacing ### with the relative location of the directory containing the scripts:

<add key="Dart.PowerWEB.TextBox.ScriptsDirectory" value="###" />

Setting the value of this node to "" will be interpreted as the current directory, relative to the page being executed. It is recommended that you place these files in their own directory and provide a value that is relative to the root of the web such as "/myApplication/TextBox_Scripts"

In This Section

Documentation Map: Provides a good navigational aid to quickly find the topic you want.
Requirements: Discusses the components that are licensed in PowerWEB TextBox for ASP.NET.
Licensed Components: Discusses the requirements needed to use PowerWEB TextBox for ASP.NET.
License Registration: Provides step-by-step instructions on installing a license.
Trial Operation: Provides an overview on using PowerWEB TextBox in ASP.NET in trial mode.
Creating the Licenses.licx File: Discusses the required 'licenses.licx' file.
Deployment: Discusses the steps that are required to distribute an application in ASP.NET.
Support Options: Provides an overview of the support options that are available for this product.

Send comments on this topic.

Documentation version 3.2.0.0.