Thursday, February 21, 2013
App_Offline.htm
Linked Reference
"App_Offline.htm" feature in ASP.NET 2.0, provides a super convenient way to bring down an ASP.NET application while you make changes to it (for example: updating a lot of content or making big changes to the site where you want to ensure that no users are accessing the application until all changes are done).
The way app_offline.htm works is that you place this file in the root of the application. When ASP.NET sees it, it will shut-down the app-domain for the application (and not restart it for requests) and instead send back the contents of the app_offline.htm file in response to all new dynamic requests for the application. When you are done updating the site, just delete the file and it will come back online.
One thing I pointed out in the talk that you want to keep an eye on is a feature of IE6 called "Show Friendly Http Errors". This can be configured in the Tools->Internet Options->Advanced tab within IE, and is on by default with IE6. When this is on, and a server returns a non HTTP-200 status code with less than 512 bytes of content, IE will not show the returned HTML and instead substitutes its own generic status code message (which personally I don't think is super friendly <g>).
So if you use the app_offline.htm feature, you should make sure you have at least 512 bytes of content within it to make sure that your HTML (instead of IE's friendly status message) shows up to your users. If you don't want to have a lot of text show-up on the page, one trick you can use is to just add an html client-side comment with some bogus content to push it over 512 bytes. For example:
"App_Offline.htm" feature in ASP.NET 2.0, provides a super convenient way to bring down an ASP.NET application while you make changes to it (for example: updating a lot of content or making big changes to the site where you want to ensure that no users are accessing the application until all changes are done).
The way app_offline.htm works is that you place this file in the root of the application. When ASP.NET sees it, it will shut-down the app-domain for the application (and not restart it for requests) and instead send back the contents of the app_offline.htm file in response to all new dynamic requests for the application. When you are done updating the site, just delete the file and it will come back online.
One thing I pointed out in the talk that you want to keep an eye on is a feature of IE6 called "Show Friendly Http Errors". This can be configured in the Tools->Internet Options->Advanced tab within IE, and is on by default with IE6. When this is on, and a server returns a non HTTP-200 status code with less than 512 bytes of content, IE will not show the returned HTML and instead substitutes its own generic status code message (which personally I don't think is super friendly <g>).
So if you use the app_offline.htm feature, you should make sure you have at least 512 bytes of content within it to make sure that your HTML (instead of IE's friendly status message) shows up to your users. If you don't want to have a lot of text show-up on the page, one trick you can use is to just add an html client-side comment with some bogus content to push it over 512 bytes. For example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Site Under Construction</title>
</head>
<body>
<h1>Under Construction</h1>
<h2>Gone to Florida
<!--
Adding additional hidden content so that IE Friendly Errors don't prevent
this message from displaying (note: it will show a "friendly" 404
error if the content isn't of a certain size).
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
<h2>Gone to Florida
-->
</body>
</html>
Wednesday, February 6, 2013
Automatically checkin files after uploading
In a typical document library of SharePoint, when use “Upload Multiple Files”, or use drag & drop in Explorer View, you can upload multiple files or folder easily. However sometimes the files are kept in “Checked out” mode and will not be available for others until they are checked in. Unfortunately SharePoint doesn’t have a “bulk check-in” function. So how do you have the files automatically checked in?
The key is in the setting “Require documents to be checked out before they can be edited” – this has to be “No”. Change it through “Document Library Settings”->”Versioning Settings”. The option is at the bottom.
Another setting that could prevent files to be auto checked in is the required columns. Make sure you turn off all mandatory columns, or give them a default value.
Other settings in “Versioning Settings” (such as Content Approval, version numbers etc) do not matter.
The key is in the setting “Require documents to be checked out before they can be edited” – this has to be “No”. Change it through “Document Library Settings”->”Versioning Settings”. The option is at the bottom.
Another setting that could prevent files to be auto checked in is the required columns. Make sure you turn off all mandatory columns, or give them a default value.
Other settings in “Versioning Settings” (such as Content Approval, version numbers etc) do not matter.
Subscribe to:
Comments (Atom)