C # web application packaging and deployment problems

Often go to the site to install and debug the customerProgramSometimes the problems encountered at the scene are just speechless, so experience is a fortune.

I found some precautions on the Internet for reference, so I checked before installing the web program.

1. Check whether the client has IIS installed. If not, install IIS. (generally, no iis is installed on the client. Therefore, the installation file must be provided)

Solution 1: Install the IIS installation package. You can download the installation package from the Internet. However, the client may not find the lite version of the system.

Solution 2: reinstall the system and install the IIS File while installing the system. In this way, no errors will occur.

For the first installation of IIS, you must configure it, such as IP configuration, application pool, and support for aspx and. Net versions,

The operating system sets the user's access permissions to files. If the website file still requires some special permissions, such as write and modify permissions,

You will know what you encounter.

2. Check whether the client is installed with. Net framework2.0 or later. If not, install it (with the. NET framework2.0 installation file)

Installing the 2.0 Framework is not simple...

3. Install the program in one of the IIS virtual directories

Generally, the installation of packaged programs is basically under the default website by default, so you can directly enter the IP address to read the package.

4. Packing SQL databases? Scripts, backup files, data files, and other methods.

Whether the database is installed, whether to connect to the database after web installation, set database security, back up and restore data files,

How to share data files in databases of different versions is much bigger than that of databases ....