How to deploy Asp.net 2.0 websites with dxperience components to servers

 

How to deploy the Asp.net 2.0 website to the server. NET 2.0 is an improvement compared with. NET 1.1. Program Without the bin directory, the reference to the class library is automatically placed in the web. config file. The advantage is that you do not need to explicitly add related DLL files in the bin directory as before, which facilitates the development process, it also caused some problems when deploying locally developed web programs to the server. Do you find that it does not work when running all normal programs locally and publishing them to the server? It is very likely that you have referenced third-party class libraries other than the. NET Framework class library in the web program.
Therefore, no matter whether you use the xcopy method, the vs pre-compilation method, the replication method, or the aspnet_compiler Compilation Method in command line mode to publish to the remote server, before that, you have to be like. in net1.1, add the bin folder under the root directory of your web program and put all third-party class libraries used on your website to this directory. Check the Web. config file to clearly know which third-party class libraries are used in your program. See the following Code Section:

1 < Assemblies >
2 < Add assembly = " Devexpress. Web. v8.3, version = 8.3.6.0, culture = neutral, publickeytoken = 5377c8e3b72b4073 " />
3 < Add assembly = " System. Design, version = 2.0.0.0, culture = neutral, publickeytoken = b03f5f7f11d50a3a " />
4 < Add assembly = " Devexpress. Data. v8.3, version = 8.3.6.0, culture = neutral, publickeytoken = 5377c8e3b72b4073 " />
5 < Add assembly = " System. Windows. Forms, version = 2.0.0.0, culture = neutral, publickeytoken = b77a5c561934e089 " />
6 < Add assembly = " Devexpress. Web. aspxgridview. v8.3, version = 8.3.6.0, culture = neutral, publickeytoken = 5377c8e3b72b4073 " />
7 < Add assembly = " Devexpress. Web. aspxeditors. v8.3, version = 8.3.6.0, culture = neutral, publickeytoken = 5377c8e3b72b4073 " />
8 < Add assembly = " Devexpress. Web. aspxspellchecker. v8.3, version = 8.3.6.0, culture = neutral, publickeytoken = 5377c8e3b72b4073 " />
9 < Add assembly = " Devexpress. Web. aspxtreelist. v8.3, version = 8.3.6.0, culture = neutral, publickeytoken = 5377c8e3b72b4073 " />
10 </ Assemblies >

Rows 2nd, 4, 6, 7, 8, and 9 reference non. net2.0 base class library, so we need to copy the corresponding DLL files to the bin directory. Is that all done? Not necessarily. Check the following code in Web. config:

< Httphandlers >
< Add verb = " Get, head " Path = " Scriptresource. axd " Type = " System. Web. Handlers. scriptresourcehandler, system. Web. Extensions, version = 1.0.61025.0, culture = neutral, publickeytoken = 31bf3856ad364e35 " Validate = " False " />
</ Httphandlers >

This code is generated when the Asp.net Ajax control is used. If you install atalas, you will know. Therefore, you must copy system. Web. Extensions. DLL to the bin directory. Of course, you may not need to use the ajax.net control in your program. You just need to handle all similar problems.

When all the necessary DLL files are copied to the bin directory, it is not far from the successful deployment, and other operations can be done step by step.

PS: Sometimes you want to test the feasibility of remote servers during website development, but this is not realistic and flexible (but reliable) for most programmers ). In view of this, we recommend that you use virtual machine testing. The virtual machine platform is wmware workstation. Install the server operating system on the virtual machine, such as Windows Server 2000 or 2003 (WINXP can also be used). After IIS and framework2.0 are installed, you can test it. For more information about virtual machines, see Google. If you have any questions, please contact me.

 

Reprinted from: http://www.cnblogs.com/loay/archive/2009/03/27/1422807.html

Dev Forum site http://smartsoft.5d6d.com/forum-132-1.html