Amar Galla’s Weblog

Hi everyone. After using Typemock on one of my projects, I can definitely say that it is a fantastic product for your unit testing. Have just heard about a promotion which Typemock is running currently to promote their new produt and giving away licences. See the details below:

Unit Testing ASP.NET? ASP.NET unit testing has never been this easy.

Typemock is launching a new product for ASP.NET developers – the ASP.NET Bundle – and for the launch will be giving out FREE licenses to bloggers and their readers.

The ASP.NET Bundle is the ultimate ASP.NET unit testing solution, and offers both Typemock Isolator, a unit test tool and Ivonna, the Isolator add-on for ASP.NET unit testing, for a bargain price.

Typemock Isolator is a leading .NET unit testing tool (C# and VB.NET) for many ‘hard to test’ technologies such as SharePoint, ASP.NET, MVC, WCF, WPF, Silverlight and more. Note that for unit testing Silverlight there is an open source Isolator add-on called SilverUnit.

The first 60 bloggers who will blog this text in their blog and tell us about it, will get a Free Isolator ASP.NET Bundle license (Typemock Isolator + Ivonna). If you post this in an ASP.NET dedicated blog, you’ll get a license automatically (even if more than 60 submit) during the first week of this announcement.

Also 8 bloggers will get an additional 2 licenses (each) to give away to their readers / friends.

Go ahead, click the following link for more information on how to get your free license.

May times when I try to design a XSL against an unknown data stream, I would like to know what all values are available. Here is a nifty XSL which I have been using for a while. ( I am sure there are many versions out there ).

<xsl:for-each select="@*">
    <br/> Name: <xsl:value-of select="name()" /> Value:<xsl:value-of select="." />
</xsl:for-each>�

It gives a list of all elements with their values. Quite handy to check if you have got the element name wrong etc.

In my previous blog entry, I showed how to configure ASP.NET to output XHTML to the browsers. However, when the W3C Validator checks the page, ASP.NET does not know the W3C user agent and hence sends out non compliant code. The trick is in the w3cvalidator.browser file available on idunno.org. Just drop the file in your App_Browsers folder and ASP.NET will send out XHTML compliant code to the Validator.

ASP.NET by default does not emit XHTML compliant code. Consider this scenario. You have carefully created an XHTML compliant design. Created your pages using ASP.NET and when you try to validate your page, it fails with the error :

Line x, Column y: there is no attribute “name”.

<form name="aspnetForm" method="post" action="Default.aspx" id="aspnetForm">

This leaves you a bit stunned, as ASP.NET adds the name tag to the form on compile and you don’t have any control over it. However, don’t worry. There is a solution.

Just add to following under system.web in your web.config file. 
<

xhtmlConformance mode=“Strict” />

ASP.NET should generate compliant code now, and you should see the following in your rendered output.

<form method="post" action="default.aspx" id="aspnetForm">

As you see, it does not render the name tag anymore. Problem solved. Time to display the W3C Validated icons on your page with pride

I recently gave Microsoft Source Analysis a try. It was released sometime ago, and act’s as an add-in in Visual Studio to check the source code with some coding rules. This is different from FxCop which checks assemblies. This checks your source code before it is compiled right in Visual Studio editor.I did like the tool. Quite handy, but will need a little bit getting used to.

Some companies may need to change some rules to match their coding standards. For people who don’t have a particularly though out coding standard in place, and are using something from the ASP / VB / C days, it may be worth changing over the standard based on the Source Analysis rules, as it has been in use for quite a while at some parts of Microsoft, and from an overall look, it does look quite a decent one.

//———————————————————————–
// <copyright file=”Program.cs” company=”Your Company Name”>
// Copyright (c) Your Company Name. All rights reserved.
// </copyright>
// <author>Your Name</author>
//———————————————————————–

// <auto-generated />

For more details about headers, you can check out the rules documentation on the Source Analysis Blog.

Lastly, now, you are sort of morally forced to document every method. I know it’s a bit of an effort for all lazy developers like me. So GhostDoc come here to rescue us from our plight. For those of you, who don’t know about Ghost Doc, shame on you. Just kidding It is a cool VS Add-In by Roland Weigelt, which auto generates method descriptions by guessing it from the description. It is not perfect, but definitely a big leap from the Visual Studio way. Download it and I can assure you that you will seriously get addicted to it. Combine together Ghost Doc and Source Analysis, make coding much clearer, better documented and developer friendly.

Shawn Burke has a nice article which explains how to enable Visual Studio to download the symbol files and enable debugging for the .NET Source Code in your project. This is definitely a big help, as we no longer have to treat internal .NET assemblies as a black box, but gives us a the power to find out why an error happened and what kind of data the runtime expects?

Have a look at this excellent article and start configuring your development environment to support it.

Just a quick update. Found this cool poster of .net 1.0 – 3.5 namespaces. Definitely a must to hang around any developer’s cubicle  Download it straight from Microsoft.