A little experience in deploying. netframework4 (Asp. net4) in win03 + IIS6

Today, the website is upgraded to ASP. net4 Based on. NET framework4 (webform ). Some minor problems encountered in the middle. Record them here. In case of any brother, it will benefit the society...

First, if you use vs2010 to open the solution, it will automatically upgrade you. After the upgrade, the Web. config will become refreshing immediately.

Compile onceProgramIt can be released later. The release function of vs2010 is very powerful. See the figure below.

Because it is out of the scope of this article, I will not elaborate on it. scottgu has someArticleI have introduced the release of this article in detail. If you are interested, you can look for it.

The next step is to upload the published site to the server through all means (FTP, etc.

Of course, before that, we should prepare. Net framework4 on the server. In fact, we can use the client profile normally. Here, I would like to comment out the size of the framework. The full version is only 40 MB, and the CP version is 30 MB (as if it was). The difficult deployment problem is solved.

The installation takes about 10 minutes.

Then, according to our habits, we will set the site's ASP. NET version. Of course we should select 4.0.30319 here (a little excited)

Then, when we were eager to browse the website, the cup happened ----- 404 !!!

After reading the ISAPI, it is clearly 4.0.

It seems that I can only find it by experience. After some twists and turns, I found this

I was so dizzy that I did not expect many things here. I didn't even pay attention to the Versions later than ASP. NET. After running is allowed, everything will be fine :)

By the way, if you select "Network Service" in the original application pool, it may cause version conflicts (for example, I have three servers). Now it seems to have disappeared, deploy an ASP. net website is really easy ~