|
Hello everyone,
I am deploying an ASP.Net web site, and there are related configurations, pages and binaries. There is also a related application pool related to this web site.
My question is, what is the graceful way to upgrade to an existing such type of web site? Drop the previous web site and install a new one? Any documetns or samples to make reference about how to write scripts to do such assignment automatically?
thanks in advance,
George
|
|
|
|
|
George_George wrote: Drop the previous web site and install a new one?
No !!
You can have a look on Copy web Tool ,Which provided with VS .
Another approches, when you publishing the sites, from Visual Studio, there is a checkbox, make Sites updateable.
Check for Overview[^]
|
|
|
|
|
Hi Abhijit,
Do you have a step-by-step Copy web Tool document or samples to make a reference? I did a lot of search but can not find. In MSDN, there is just document like this, what I want to have is a step-by-step guide tells me which menu I should click and fill-in what value. The MSDN document tells nothing about this topic. Thanks.
http://msdn.microsoft.com/en-us/library/1cc82atw(VS.80).aspx[^]
regards,
George
|
|
|
|
|
George_George wrote: My question is, what is the graceful way to upgrade to an existing such type of web site?
Is that website up and running currently? If yes, the most used method is to take the website down at the time of upgrade. Show users a nice message describing the upgrade and expected uptime. Read about app_offline.htm file.
|
|
|
|
|
Thanks Navaneeth,
Why not using online upgrade approach? What are the major issues?
regards,
George
|
|
|
|
|
George_George wrote: Why not using online upgrade approach?
I didn't get that. Do you mean deploying without taking the site down? If yes, that may show some incorrect results for visitors as some part of the program is getting updated. When the assemblies or config files changes, ASP.NET will recycle the worker process which will make the site slow. It is better to take it down, do the upgrade and put it back online.
|
|
|
|
|
Thanks Navaneeth,
1.
"ASP.NET will recycle the worker process which will make the site slow" -- Do you mean ASP.Net will automatically detect binaries files change (under bin folder)? Why it will make system slow?
2.
If I "deploying without taking the site down", I am not sure whether clients of the web site will met with errors during the upgrade process -- I have this confusion because I am not sure whether the existing worker process which is using old version dll (which is replacing with new dll under upgrade process) will have issues?
regards,
George
|
|
|
|
|
1 - yes. It finds changes made to assemblies and configuration files. When a request comes for a page, ASP.NET has to compile it which will make it slow for the first time (Assuming you are not using precompiled deployment).
2 - This can't be predicted. It completely depends upon your code.
|
|
|
|
|
Thanks Navaneeth,
1.
I think if we do online upgrade, we just make the response slow since ASP.Net needs to compile it. But if we shutdown web site, no response could be served. And at the first time, ASP.Net also needs to compile. So, why not select online upgrade solution?
2.
I am confused about what do you mean ASP.Net needs to compile. I have compiled/build the binary code into DLL (as web handler bianry file), why ASP.Net needs to compile again?
regards,
George
|
|
|
|
|
1 - You are repeating the same question. I will try to explain once more. Assume you have 100 users online when doing a site upgrade. All 100 will have some data on their session or whatever it is. When you upgrade the files, ASP.NET recycles the worker process and all the above said sessions will be lost. If your application is not written defensively, it will throw error user in many places.
This is bad and user is not aware of the upgrade. So to prevent all these, a usual practice is to take the site down when upgrading. This method also clears the sessions and other data, but user is informed so that he won't be in a confusion that what's wrong with the application.
2 - If your site is precompiled, ASP.NET will not compile it again. But still you will notice a performance degrade when requesting the page for the first time.
|
|
|
|
|
Thanks Navaneeth,
1.
"When you upgrade the files, ASP.NET recycles the worker process and all the above said sessions will be lost." -- do you have any documents to prove this point? Just want to learn more.
2.
"precompiled" -- you mean build into managed code DLL? I think all ASP.Net application is precompiled since we always encapsulate function into DLL and DLL is compiled. Any exceptions which are deployed but not precompiled?
3.
"still you will notice a performance degrade when requesting the page for the first time" -- because of JIT managed code into native code for the 1st time?
regards,
George
|
|
|
|
|
1 - I don't remember any documents right now. But I believe all good ASP.NET books explains this.
George_George wrote: "precompiled" -- you mean build into managed code DLL? I think all ASP.Net application is precompiled since we always encapsulate function into DLL and DLL is compiled. Any exceptions which are deployed but not precompiled?
ASP.NET allows many types of deployment. It allows you to just copy the ASPX and code behind files to server and which will be compiled when it is requested. Precompiled method produces assemblies and you only need to copy ASPX files and those assemblies
George_George wrote: "still you will notice a performance degrade when requesting the page for the first time" -- because of JIT managed code into native code for the 1st time?
Yep.
|
|
|
|
|
Thanks Navaneeth,
1.
"But I believe all good ASP.NET books explains this." -- could you recommend one or two ASP.Net books which you think is good? I trust your recommendation as you are guru here.
2.
"ASP.NET allows many types of deployment" -- interested. I want to learn more about different ASP.Net deployment modes. Do you have any recommendations for documents/samples for that topic? 
regards,
George
|
|
|
|
|
George_George wrote:
Why not using online upgrade approach? What are the major issues?
Navaneeth has already given you the answer. I just want to add few point.
For upgradation of sites , some times you need Reset IIS , which will reset your all Session and Cache data. Which will impact badly on live user.
So if you are going to update a live site, first down it as navaneeth suggested and then update it.
|
|
|
|
|
Thanks Abhijit!
Informative answer.
1.
"which will reset your all Session and Cache data. Which will impact badly on live user." -- I am interested in what happens. Do you have any further documents to make a reference?
2.
I think if we shutdown web site, it is the same -- all session and cache are missing. Any comments?
regards,
George
|
|
|
|
|
George_George wrote: hanks Abhijit!
Welcome !
George_George wrote: 1.
"which will reset your all Session and Cache data. Which will impact badly on live user." -- I am interested in what happens. Do you have any further documents to make a reference?
You can read out some more concepts like Application Pool, Web Gardens etc.
If you are more interested on caching, you can read one of my article in CP.
Exploring Caching in Asp.net[^]
George_George wrote: 2.
I think if we shutdown web site, it is the same -- all session and cache are missing. Any comments?
Not always - For session, it will be happen in the case of Session State inproc. But I think for SQL Server Session mode it will be available.
Anyway, Thanks for your interest . Let us know if you have any issue.
modified on Wednesday, December 17, 2008 8:25 AM
|
|
|
|
|
Thanks Abhijit,
1.
I have read the document you mentioned. It describes quite well about how Cache works in ASP.Net, but never mentions what impact will be for cache when we do online upgrade for the web site, also it does not mention impact to session during online upgrade scenario. Any more descriptions or more documents to make recommendations?
2.
What do you mean "For session, it will be happen in the case of Session State inproc. But I think for SQL Server Session mode it will be available." -- more description please?
regards,
George
|
|
|
|
|
1 - Cache will be lost. If session mode is InProc, it will also be lost.
2 - Yes SQL Server session mode will be available.
|
|
|
|
|
Thanks Navaneeth,
1.
"If session mode is InProc" -- I am interested in different session mode, and I did not aware of any different session mode before for ASP.Net application. Do you have any good documents about this topic to refer?
2.
"SQL Server session mode will be available" -- what is SQL Server session? Do you mean SQL Server connection?
regards,
George
|
|
|
|
|
1 - here[^] you go
George_George wrote: what is SQL Server session? Do you mean SQL Server connection? Smile
NO. Session can be kept on SQL server database. Usefull for applications hosted on webfarms.
|
|
|
|
|
Thanks Navaneeth,
I like the link you recommended. I have a further question, it is useful to use SQL server or use ASP.Net state process if I only have one web server (not a server farm)? I am not sure whether SQL server or use ASP.Net state process are solutions specifically for multiple server (server farm) environment?
regards,
George
|
|
|
|
|
Hi,
I need to post my application 's link to orkut (scrapbook or profile) by getting orkut username & password from the user & post my application's link in his orkut scrapbook or profile.
Note:
In this following link
http://www.quibblo.com/quiz/3b_qEvo/Have-you-finished-your-Holiday-gift-shopping-yet
To the right side of the page you can see YOUR QUIZ TITLE WILL GO HERE ,below that option are there to post the current link to orkut,...i need to implement that functionality ... ie i need to post my application link to orkut)
Please help me with regard to the problem.
|
|
|
|
|
prabhuch85 wrote: I need to post my application 's link to orkut (scrapbook or profile) by getting orkut username & password from the user & post my application's link in his orkut scrapbook or profile.
I don't think you will able to do it unless orkut provides you some web services.
|
|
|
|
|
Hi i wanna to implement rating system for my web page
with same user can vate only onece
|
|
|
|
|
use some database to track the user whether he voted or not corresponding to the specific item.
You can also save the IPaddress to prevent more than one post from the same IP.
Cheers!!
Brij
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
