Last post Jan 19, 2009 05:59 AM by kimoy
Jan 15, 2009 05:34 AM|kimoy|LINK
I'm wondering if anybody can point to me a good resource about creating hotfix for websites. Currently, we always send out the entire website application to our clients even if the fix is only for a few pages.
Jan 19, 2009 05:33 AM|Thomas Sun – MSFT|LINK
From your description, I understand that you want to update partial pages after website is deployed on IIS, right?
I think it depends upon how we deploy it on IIS and what we change on the page.
If we deploy website with source code on IIS directly, we can only copy changed pages to server. Because ASP.NET website can be compiled at runtime.
We can precompile website with "Updatable", we can make limited changes, such as change the arrangement of controls, colors, fonts, to the ASP.NET Web pages.
For more information, see ASP.NET Web Site Precompilation Overview (http://msdn.microsoft.com/en-us/library/399f057w.aspx).
I look forward to receiving your test results.
Jan 19, 2009 05:59 AM|kimoy|LINK
Since we are sending it to our clients, we are only sending a precompiled site, and not the sourcecode.
Please bear with me for not being specific in my original post. Days ago, I found a critical bug in one of the pages of our website which I eventually fixed. I basically don't like the idea of sending an entire website just because of a bug in one of the
pages regardless if it's critical or not. So I dug, checking the .COMPILED file of the page I had just had a bug fixed, and realized that I can just copy-and-paste the page and the assembly this precompiled page is referring to to our client's server to fix
To make sure that this would work, I had tested this out on one of our servers where an instance of the "buggy" version of the website was deployed but it didn't work. Upon opening the page with fixes, IIS complained that a certain page is not precompiled.
I then realized that the page that I had fixed have some dependencies as defined in the <filedeps> of the .COMPILED file. After copying-and-pasting the dependent files to our test server, it finally worked!
Now, my question should have been, is there any convenient way to send a fix other than checking the .COMPILED file, looking for the assembly the page is referring to, and likewise checking for its dependent files one-by-one?