Arne Brachhold

First places are not really surprising, but tenth place for USA after Denmark?

(Image was fitted for correct display)

See the full statistic on Google Trends

If you’re working in a team on a .Net project, all devs should use the same coding guidelines as well as the same code formatting. Visual Studio 2005 has powerful options to automatically format your code how you like it. Unfortunately there is no way to export this settings from Visual Studio, so every developer has to configure the formatting settings by hand.

This is not very comfortable and fail safe so there must be a way to export or backup these settings, so you can import them on an other computer or ideally set them as a group policy in Active Directory.

(Read on …)

This is a little Microsoft .Net class which allows you to use the powerful Akismet comment spam protection in your .Net wiki/blog/website/software.

It’s well documented and available as a precompiled library or C# project. It’s compiled as .Net 1.1, but also works great with 2.0. Note that you need to obtain a WordPress.com API key to use it.

(Read on …)

Custom Webhandlers are an excellent method to create ASP.Net pages which don’t need all the Page and WebControl stuff. Maybe you already created a .aspx file which should only return XML or an image.

If you develop with Visual Studio, it creates automatically an .aspx and .cs file for you and you have to delete all content except the Page Directive from the .aspx file or call Response.End() at Page_Load. This is not very cool and results in useless work.
(Read on …)

Microsoft released the new Microsoft Component Installer Software Development Kit which is a SDK to perform various required installations for your .Net application.

The installer includes:

If you run it before your application setup, you can be sure all required components will be installed.

You can also specify an application or URL which will be executed when the installer finished. If you set the the "uionlyifneeded" parameter, the installer won’t be shown to the user if all required components are already installed.

If you code in a team, it is important that you use the same code style, especially if developers began with different languages which had individual styles. For example, PHP is often coded with camelCase and C++ developers use prefixes like strName or intZipCode.

Modern IDEs allow you to see the type of your members or variables while working with them. Visual Studio shows the type in the Intellisense window, Eclipse has a similar function for Java.

Mixing coding styles makes it hard to read the code and find members via AutoComplete.

So you should apply company-wide coding guidelines, use them and correct wrong names.

For the .Net Framework I recommend to use the Naming Guidelines for the .Net Framework. You can check your Assemblies using a tool called FxCop from GotDotNet.com. FxCop also provide checks for performance, design and security issues.

You can also specify custom rules if the existing rule library doesn’t fit your needs.

A good way to enforce coding guidelines to all developers is to add the code formatting settings to the Active Directory. These settings are saved in the registry, so you can import or export them easily.