2012VS Release web--News system release process and error analysis

Finally began to publish the system, so happy Ah, now the news release process and the release process to summarize the errors generated.

Release Process:

1 System Regeneration--click Publish in the Web

2 Click Post-The following page appears--click New--Write the name you want to give the system

3 Click the connection, the following page appears, publish the way to select "File System", the target location is the physical address of the folder where we will publish the system

4 Set the default "Release" on it.

5 Next, click Publish, we can see our system will show the success of the release.

6 Next look at IIS (Internet Information Services Manager), which is also a Web server. See http://baike.haosou.com/doc/3171310-3342126.html for his usefulness and more explanations.

Right-click on the site-Choose Add site (This is what I added is Test), and then fill out our site name, where the application of the program pool is our default DefaultAppPool. The physical address is the path to the folder where we published the system above. Then fill in the IP number of our room. Also in order to prevent the release of the system too much, port blocked, change a new port.

7 Assign permissions to the user. We click "Connect as"--Select specific user--write the username and password of our computer and click OK.

8 Click Test Settings-we see that our authentication and authorization are already checked.

9 Click on our website and click on the content view. Then, on the page that we want to open, right-click-Choose Browse, and you can see our published page.

To achieve the above points, under normal circumstances can be successfully browse the site.

Because you want to visit your website on someone else's computer, you need to turn off the firewall (Control Panel-firewall)

Error Rollup:

Since we have set the error page, we jump to the error page and then jump to the home page when we make a mistake. So we can not see the error, so before making a mistake to comment out the error page, to see if it is the wrong report.

1

There are many answers to this question online, please see the link http://blog.csdn.net/renpinghao/article/details/6423353

If your computer is a 32-bit operating system, there is a problem above, you can look at the blog of the elder sister. Http://blog.csdn.net/mazhaojuan/article/details/7660657#comments

My is 64-bit operating system, according to the operation of the sister-in-the-line blog, my always unsuccessful. After the path has been replaced, the execution succeeds.

At that time, I think, since this update is V2.0, then in IIS, I should also choose 2.0, Internet Check know if I choose V2.0, then the pattern is classic, not our default integration, the page is as follows:

But still unsuccessful, the problem still remains. (I think the scheme is still feasible, but the execution is not successful, do not know why)

Since the default is v4.0, and the default managed pipeline mode is integration, we can use a setting to start up a 32-bit. Choose our v4.0, right-click-Select Advanced Settings-enable 32-bit application to true, the problem just solved!

2 after the system entered, click Add News, but reported this error, I run in the VS is no problem, why after the release of the error?

I began to think it must be the path of the problem, because the beef brisket teacher said the absolute path, relative path What, I think I easily confused, about the path of the explanation, see the elder sister blog http://blog.csdn.net/wangdan199112/article/details/38110209

I looked at my code, no mistakes. After checking the Internet, I changed it a bit. Success.

The above is my re-write code, the following is the previous code, write-off. What are the differences and connections between CodeFile and codebehind?

The original is CS file is not compiled in. for the development, that is, the page logic code CS file exists, the subordinate two kinds of writing no problem.

<%@ page language= "C #" autoeventwireup= "true" codebehind= "Index.aspx.cs" inherits= "Community.IndexHomePage.index "%>

<%@ page language= "C #" autoeventwireup= "true" codefile= "Index.aspx.cs" inherits= "Community.IndexHomePage.index"% >

However, after deploying to the site, we will not deploy CS file, this time, the latter method will be reported to find the error of the file. Unless you deploy CS Also, you will be reported compile-time errors, files cannot be found.

For a detailed distinction, see http://www.360doc.com/content/11/1221/20/6856598_174058525.shtml

In the publishing process, there are other errors, such as not the BLL file under the DLL control AspNet.ScriptManager.jQuery.dll also released the past. I had to copy and paste it under the BLL of the publishing system, and I'm not sure what went wrong.

Overall Experience:

Release is a very small link, but these days have been published, the overall harvest is still a lot. The later study will be more exciting, at the same time summary is also an important part of learning, let csdn better record of our learning harvest and feel it.

2012VS Release web--News system release process and error analysis