Deploying ASP.Net 2.0 Application
I have to admit that the logistic of messing with ASP.Net 2.0 is pretty new to me, but now that I have a chance to do the study and actually try out deploying ASP.Net 2.0 in a production environment, I don't want to pass the opportunity. Here are the steps and some tidbits about how to get it working:
- First finish the web application in Visual Studio .Net 2005
- Use Deploy Site to deploy the clean files (without source code and such) into a directory.
- On the server, created a new virtual directory, and set it to run ASP.Net 2.0
- Copy the files to the virtual directory.
If something failed, then maybe this is the first time the site having ASP.Net 2.0 deployed. You can fix the problem issues accordingly.
- If you got "Page not found", it's possible that ASP.Net 2.0 scripts was not being installed properly. First change directory to "drive:\%windir%\Microsoft.NET\Framework\v2.0.50727" then execute "aspnet_regiis.exe -sn W3SVC/1/ROOT/YourNewAppVirtualName". The problem should be fixed by then. [Reference]
- If you get "The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'." error, then need to make ASPNET account to have all the right on the "Temporary ASP.NET Files" directory. Make sure that you set it so that all the child folder also have that kind of privilege. [REference]
I can foresee that more prblem will be coming but ... oh well .. one at a time.
- First finish the web application in Visual Studio .Net 2005
- Use Deploy Site to deploy the clean files (without source code and such) into a directory.
- On the server, created a new virtual directory, and set it to run ASP.Net 2.0
- Copy the files to the virtual directory.
If something failed, then maybe this is the first time the site having ASP.Net 2.0 deployed. You can fix the problem issues accordingly.
- If you got "Page not found", it's possible that ASP.Net 2.0 scripts was not being installed properly. First change directory to "drive:\%windir%\Microsoft.NET\Framework\v2.0.50727" then execute "aspnet_regiis.exe -sn W3SVC/1/ROOT/YourNewAppVirtualName". The problem should be fixed by then. [Reference]
- If you get "The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'." error, then need to make ASPNET account to have all the right on the "Temporary ASP.NET Files" directory. Make sure that you set it so that all the child folder also have that kind of privilege. [REference]
I can foresee that more prblem will be coming but ... oh well .. one at a time.
0 Comments:
Post a Comment
<< Home