The Deployment Manager can be used with ASP.NET applications to collect all of the .aspx, asax, Web.config and other assembly files, as well as related assemblies.

1. Open the ASP.NET project that you want to deploy. In the Project Manager window, right-click the Deployment option under the library that corresponds to your project name.
2. Select New ASP.NET Deployment. This opens the Deployment Manager window. There are three main categories of files: ASP.NET Markup Files, Executables, and Config Files.
3. The strong name assemblies Borland.Data.Common.dll and Borland.Data.Provider.dll have traditionally existed in the Global Assembly Cache (GAC). Add these two files to the project directory by right-clicking References under the library that corresponds to your project name and then selecting Add Reference. Click each of the file names and then click Add Reference. After both references appear in the lower section of the Add Reference window, choose the OK button.
4. Open the References node of the library tree, and the new .dll files are listed. Select each of the .dll files that you added in the previous step, and set the Copy Local Assembly Property in the Project Manager to True.
5. Right-click References again to add your database-specific .dll file(s) to the assembly. For instance, if you are running MySQL Server, you would add the Borland.Data.Mysql driver and set the Copy Local Assembly Property in the Project Manager to True.
6. Recompile your project.
7. Highlight your deployment window again under the Deployment option of the Project Manager window.
8. Browse or enter a path to the target machine, where you want to deploy your application. Then click the icon next to each file name. This moves each file to the 'Destination' side of the window. When all of your source files appear on the 'Destination' side of the window, they have been deployed to the target computer.