<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Martijn's C# Programming Blog &#187; code guidelines</title>
	<atom:link href="http://www.dijksterhuis.org/tag/code-guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dijksterhuis.org</link>
	<description>Information, news about programming in C#</description>
	<lastBuildDate>Fri, 07 Aug 2009 21:26:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>C# guidelines that improve your code quality</title>
		<link>http://www.dijksterhuis.org/csharp-coding-guidelines/</link>
		<comments>http://www.dijksterhuis.org/csharp-coding-guidelines/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 08:25:37 +0000</pubDate>
		<dc:creator>Martijn</dc:creator>
				<category><![CDATA[Review]]></category>
		<category><![CDATA[code guidelines]]></category>

		<guid isPermaLink="false">http://www.dijksterhuis.org/?p=873</guid>
		<description><![CDATA[I am inspired to better myself after reading Dennis Doomen&#8217;s freshly released coding guidelines for C# 3.0 . He provides a very nice PDF document that puts the dot to many common C# coding &#8220;confusions&#8221;. It addresses how to consistently name your variables, namespaces, classes and assemblies. He specifies when to declare a variable as [...]<p>This is a post from <a href="http://www.dijksterhuis.org">Martijn's C# Coding Blog</a>. </p>
]]></description>
			<content:encoded><![CDATA[<p>I am inspired to better myself after reading Dennis Doomen&#8217;s freshly released <a href="http://www.dennisdoomen.net/2009/03/new-coding-guidelines-for-c-30.html">coding guidelines for C# 3.0</a> . He provides a very nice PDF document that puts the dot to many common C# coding &#8220;confusions&#8221;. It addresses how to consistently name your variables, namespaces, classes and assemblies. He specifies when to declare a variable as static, as readonly and when to seal a class among others. </p>
<p>Another topic he pushes is code readability and ensuring that all code statements are as clear as possible. </p>
<p><img src="http://www.dijksterhuis.org/wp-content/uploads/2009/03/screenshot.png" alt="Example Coding Guideline" title="Example Coding Guideline" width="561" height="250" class="alignright size-full wp-image-874" /></p>
<p>You will often have your own way of doing things. A shared coding guideline is a good way to ensure that each member of your team is writing code styled as similar as possible.</p>
<p>If your company is looking at adopting a coding guideline for its C# development this would be a very good place to start. </p>
<p>At 32 pages it might seem a little long at first but it reads quickly and most topics should already be familiar if you do a lot of coding. Its companion quick reference guide neatly puts most key items onto a single page and makes for a great handout.</p>
<p>This is a post from <a href="http://www.dijksterhuis.org">Martijn's C# Coding Blog</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.dijksterhuis.org/csharp-coding-guidelines/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
