ASP.NET Server.Transfer Vs Response.Direct

In essence:

Response.Redirect simply sends a message back to the browser, telling it to move to another page.

whereas

Server.Transfer conserves server resources. Instead of telling the browser to redirect, it simply changes the “focus” on the Web server and transfers the request. This means you don’t get as many HTTP requests coming through, which should ease the pressure on your Web server and make your application run faster.

Keep in mind though, because the “transfer” process can work on only those sites running on the server, you can’t use Server.Transfer to send the user to an external site. Only Response.Redirect can do that!!

Microsoft Sandcastle

Microsoft Sandcastle used to document code

http://blogs.msdn.com/sandcastle/

http://msdn2.microsoft.com/en-us/vstudio/bb608422.aspx

Enabling Intellisense in Skin files

http://vladimir.bychkov.info/blog/PermaLink,guid,be76b3bf-c524-456c-9c8f-a2584924aa32.aspx

http://www.codeguru.com/vb/vb_internet/aspnet/article.php/c7937__3/

Styling ASP Web Controls with CSS

A decent site showing the styling of various web controls.
http://samples.gotdotnet.com/quickstart/aspplus/doc/webtemplates.aspx

Using System DSN in connection strings section of web.config

<add name="connectionname" connectionString="Dsn=DSNNetData"
providerName=”System.Data.Odbc” />

Opitmistic Conccurrency

A good discussion and example of the benefits of optimistic concurrency
http://msdn2.microsoft.com/en-us/library/aa0416cz.aspx