Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall
Now the website mainstream language C # has occupied an irreplaceable position, I believe there are a lot of friends want to learn. NET, for this reason, Lee launched the system's. NET C # tutorial. I'm going to lead you all the way into. Net.
For many novice friends, perhaps the initial problem is not how to use C # to write a program, but how to build a. NET Server environment. Today, I'm going to start by teaching you how to deploy a. NET Server environment in a windows2003 server. Hope to be helpful to the novice friend.
1. Install IIS
Installing IIS requires windows2003 I386 source files. When you are ready, use Windows Add/Remove Windows Components to open the window and select the application server. Figure:
And then we just keep clicking the next step, we may be prompted to insert the Windows2003 installation CD, we directly select our prepared installation files. Until the installation of IIS is complete.
2. Installation Framework. NET 2.0
This version was chosen primarily in the light of the fact that most space vendors currently offer a. NET environment that is 2.0-oriented and most compatible. Of course, you can also install 3.5 or another version, there are two installation methods, a direct to the Microsoft website Download framework. NET 2.0 installation package installation, here need to remind everyone is sure to pay attention to the corresponding server system language, I have seen someone download the traditional version of the program installed in the simplified version of the system. Another approach is to install VS on the server directly, I recommend installing VS2005 because VS2005 has a. NET 2.0 installation package and is running as a server, personally feel that this version is more appropriate. and later server maintenance is also more convenient, so more recommended this method.
3. Configure. Net
In fact, the installation of. NET is relatively simple, if you first installed on the server after IIS, then install VS2005, in fact, the environment needs of the software will be all the default for you to install. such as vs2005,sql2005,.net2.0. Next, we enable. NET and facilitate the deployment of a. NET Web site.
First, we open IIS and choose a Web service extension, as shown in figure:
Set the ASP.net V2.0.50727 to allow
Second, we create an application pool for the new site (many friends like to use a single program pool for multiple sites on a server, which I think is not recommended and error prone).
Also, in IIS, right-click the application pool, select New, and select an application pool. Then enter the name and we take test as an example
This completes the creation of the program pool.
Finally, let's deploy a website. Right-click the Web site on the left side of IIS, select New, and then open the Web site to create a new wizard. Site description Fill test[According to the actual need to identify, such as the binding domain name can be entered, so that when a server has more than one site is easy to identify. ]。
Fill in the main header and TCP port, if the binding domain name, the general port defaults to 80. We test, so do not bind domain names, fill out an arbitrary port.
The host header fills in the bound domain name.
Then select the path of the site source code.
Last SELECT Permissions
Finally, right-click Web, properties, home directory, select the application pool we just built for the program pool.
[Article from the Triad Network www.3hcn.com Reprint please explain the source]
It is worth reminding that the general our site is not to give full control of the permissions, only for the specific circumstances of the site to the pre-partial directory Write permission.