Erwin's Blog

A common task in a project is preparing your for a deployment. The easiest way to do this is making use of a Web Setup Project. But how do we make this Web Setup Project suitable for multiple environments, because it's most likely that there are environments like Development, Test, Acceptance and Production.

Yesterday jQuery released their new version, number 1.3. They did a lot af changes / bugfixing, performance improvements.

Most people use alert() to debug their JavaScript, but the Microsoft Ajax Library has a better alterative Sys.Debug. Sys.Debug has some methods for logging messages to the browser console. Like this:

More and more ASP.NET developers are going to use jQuery. jQuery is a fast and easy to use javascript framework.

Every now and then there are situations when you have no source code available, because you lost it or you don't get it. There are some solutions to see or get the source code, with Reflector you can see the source code but you can't edit it, but with reflector you can do a lot more.

Today I was looking for a solution how to detect when a client is a search engine crawler, you can create a fancy solution for this, but in the .NET framework their is already a solution to detect search engine crawler. The property Request.Browser.Crawler. If you use this property you always get false even if the site is visited by a search engine crawler, that's because it's not configured in a default installation of .NET.

ASP.NET uses the <browsercaps> section in machine.config or web.config to determine the client browser is a crawler or not. In the default installation the crawler filter information is all blank,  that's why you'd always get false. To fix this problem, you should add the search engine crawler filters in the <browsercaps> and add this section to your web.config. Like this:

Microsoft has released a new cool charting control. It comes with documentations, samples and a lot of features, features like:

If you have a querystring from for example the Uri class (Uri.Query) and you want to parse it so you can get al the params and values, instead of doing al lot of string manipulation you can use a very handy utility class, the HttpUtility. The HttpUtility class has a method ParseQueryString, this method parse a query string into a namevaluecollection. Like this: