If your ASP.NET application does not require changes to IIS settings or registration of COM objects, and if it does not use assemblies in the GAC, you can copy the files your application needs to the production server using a simple copy technique such as the xcopy command-line tool or FTP.
If your application needs IIS configuration or uses COM objects that must be registered, or if it uses shared assemblies that are stored in the server’s global assembly cache (GAC), you might need to use another technique. For more information about deploying ASP.NET applications, see your Microsoft documentation.
DataWindow .NET provides a way to simplify deployment of DataWindow .NET runtime files using a Microsoft Windows Installer file. See “Using the Runtime Packager”.
If your DataWindow .NET application specifies a path for dynamically generated files, make sure that the ASP.NET account (or, for Windows 2003 server, the IIS_WPG user group) has write permission to the directories. You need to do this if your application uses graphs in Web DataWindows or saves the JavaScript, XML, XSLT, and CSS files generated for XML or XHTML Web DataWindows into separate directories.
For more information about setting permissions for ASP.NET applications, see the Microsoft documentation.
If your application uses the Print method or the SaveAs method with the argument Pdf to print Web DataWindows, you need to take the same configuration steps on the production server that were required on the development server. For more information, see “Printing Web DataWindows”.
If you plan to use DBCS characters, such as Chinese, Korean, or Japanese, with the Web DataWindow, you need to configure the server to handle them. This configuration is required if you want to save a DataWindow object that contains DBCS characters to text, CSV, or Excel files that use ANSI encoding, or import text or CVS files containing DBCS characters into a DataWindow object using ANSI encoding.
The regional settings you set in the Windows control panel on the server apply to the current user, not to the ASP.NET account under which the Web application is running. The regional settings used by IIS are the settings that were in effect when IIS was installed. Changing the locale on an English Windows operating system does not resolve the problem. There are three ways to resolve this issue:
Run IIS on a Native Language Windows operating system.
Set the regional settings you need before installing IIS.
Change the user account that starts running IIS from the default ASP.NET user account to a user account with the regional setting you want. To do this, you need to edit the <processModel> section in the server’s machine.config file or the impersonate setting in the web.config file. Windows Server 2003 requires a different technique.
For more information, see your Microsoft ASP.NET documentation.
