We recently migrated a clients domain from domainA.com to domainB.com. If you are familiar with search engines and indexing, migrated domains that do not have proper 301 redirects pointing from the old domain to the new will cause the new domain to miss a lot of search engine traffic. The new domain will in fact have to start all over again and get re-indexed by search engines which can take months. How do you implement a global HTTP 301 redirect? In ASP.NET, it requires editing the global.asax's application_beginrequest event...

A little while back I designed a simple social networking website for a client making use of UrlRewriter.net for rewriting their dynamic url's into readable static url's. After a couple of months I realised that Google was not indexing these pages and so I started doing a bit of digging. What I found was that Google made updates to their crawler's browser information, identifying the crawler as a Mozilla type browser. Previously the Google crawler identified itself as a generic browser within ASP.Net...

I've recently ran into a bit of trouble with maintaining the aspnet session state across a subdomains of the same application. The main problem was that the ASPNET SessionID cookie by default points to the full web address, meaning that when you navigate to a subdomain, aspnet creates a new SessionID cookie for that subdomain and doesnt read the root domains session cookie. In short, you loose your session variables/authentication info when you browse to subdomains of your site.

There are times where you require web methods like Server.HtmlDecode and Server.HtmlEncode for use within your business layer. To get access to these methods one needs to firstly add the System.Web reference to your application...

Asp.NET 2 has a new class System.Web.VirtualPathUtility which allows you to resolve relative url's without the need of working within a UserControl or Page. This is especially useful if you need to resolve relative url's from within a data layer or object interface.