Since the introduction of the var keyword in the C# 3.0, its use has been strongly debated. I have waited for some time to let the dust settle before forming an opinion.

The main argument against its use that I hear most is the use of var can make source code less readable for others.

foreach (var item in someList) {…} // Type of 'item' is not clear.
var something = someObject.SomeProperty; // Type of 'something' is not clear.
var something = someMethod(); // Type of 'something' is not clear 

As I see it the problem is not with the use of the var keyword but with the use of vague variable names. You should be using descriptive variable names.

foreach (var customer in customers) {…} // Type is clear.
var orders = customer.Orders; // Type is clear.
var order = GetOrder(); // Type is clear 

If you still need validation of the type. Hovering over the var keyword will show you the type.

I think that it reduces code noise. In the case that you wish to keep a list of customer order in memory and interate over it or get it count later. I would rather use:

var order = custer.Orders; 

Rather than:

ObservableCollection<Order> order = custer.Orders; 

The type name is just noise to me. If you use a generic list, then what is the difference than using var as well?

C# is a strongly typed language. You can check the MSDN documentation here. It states that an implicitly typed local variable is strongly typed just as if you had declared the type yourself, but the compiler determines the type.

Using the following method:

public int ReturnValue()
{

					var a = 5; 

					int b = 5; 

					return a + b; 
}
			

The IL will look like the following. Notice that both the int and the var compile down to an int32.

.method public hidebysig instance int32  ReturnValue() cil managed
{
  // Code size       9 (0x9)
  .maxstack  1
    .locals init ([0] int32 result,
    [1] int32 CS$1$0000)
  IL_0000:  nop
  IL_0001:  ldc.i4.5
  IL_0002:  stloc.0
  IL_0003:  ldloc.0
  IL_0004:  stloc.1
  IL_0005:  br.s       IL_0007
  IL_0007:  ldloc.1
  IL_0008:  ret
} // end of method VarKW::ReturnValue
				

You should have nothing to fear with the use of var were appropriate. In my experience it only helped me to create good decoupled design of my components.

I got Rock Band 2 for my family this Christmas, the rig in a box, wireless guitar, drums, mic and game disk in a big box. I have to say it was a big hit. Once I hooked it into the big screen and 5.1 surround system in the family room it was all over. We can't seem to stop playing it. The drums are somewhat realistic to playing a real trap set. The guitar playing is so silly it is fun. Now the vocal bars that scroll across the top really keep you on key. So be sure to check out my show when I come to your town.

When it comes to teamwork and mission execution, the United States Marine Corps (USMC) epitomized this concept. The USMC is the most elite fighting force in the world—and with good reason. Teamwork is the key ingredient to accomplishing any mission, and it's something Marines do very well. After all they've been doing it for over 230 years. Though this, a long tradition has formed a set guiding principles that make the USMC more successful than any other fighting force in the world.

I served for four years and learned that these Corps Principles (pun intended) are a part of me. I have found that I can apply them to my day to day work as a software developer. Doing so has made me and the teams I have worked with more efficient.

I will start to blog about these Corps Principles and how they can be applied to the software development process. Some of what I write will seem like common sense (an uncommon thing in some organizations). There may be a good chance that you will already be practicing them, and are more effective because of it. However, it has been my experience that following these principles will not guarantee success, but not following them will guarantee failure.

If you have not seen this or heard about it yet check it out here. It is only two years away. I know of many companies that are still VS2003. Although I have been using VS2008 exclusively for all my development for some time now, I have clients and colleagues alike that are fearful of some of the new language enhancements and refuse the use them. I.e. type inference, etc. I have embraced them and learned to use them properly. If type inference scares you, getting ready for dynamic object types. I also am seeing a big push from Microsoft the use of generating code from modeling. I can see much resistance to this as well. 

I'm sure that x86 assembler developers resisted when C first came about. Or C++ developers resisted when VB6 came out. Ultimately, there will always be a market for good developers, irrespective of what language tools you use. You can't learn good coding practices just because a new language tool comes out that makes constructing code easier.

My dad always told me, "It is not the tools in your toolbox that make you a good mechanic; it is how and when to use them that does."

Have you ever wished to just start up the WebDev.WebServer for the current web project you are working on? Many times I am just editing the page markup and do not have a need for the debugger nor the need to build the project. I just need to see how the page looks. Here is how I do it...

Step 1: From the 'Tools' menu select the 'External Tools...' option. This will bring up the 'External Tools' dialog.

Step 2: Select the 'Add' button. Then complete the form like so:

Set the 'Title' to a value you desire.

Set the 'Command' to %ProgramFiles%\Common Files\Microsoft Shared\DevServer\9.0\WebDev.WebServer.exe

Set the 'Arguments' to /port:3786 /path:$(ProjectDir)\ (you can set the port value to any port you desire)

Set the 'Initial Directory' to $(ProjectDir)

 Step 3: Click 'OK' button to close the dialog.

Add Done! Now you should have a new menu option on the 'Tools' menu matching the title you gave the WebDev.WebServer. When selected it will kick off the WebDev.Server utility for the current selected project on your solution.

My new blog is using Microsoft Office SharePoint Services (MOSS) 2007. I have seen Microsoft SharePoint blogs quickly become very popular among the blogging community.

I have never been much of a blogger. I hear the word blog almost daily, referred to many times as the Blogosphere. I just want to be a part of it. The great thing about blogging is that it has a community feeling. It's an informal post, a comment, an idea, a criticism, or even shout-out to the world.

Blogging has become so much more than a fad, a hobby, or even a broad-brush community. It has revolutionized how quickly people can share their thoughts, ideas, insight, - Information. I cannot count the number of times I have found the answer I was looking for right in someone else's blog. All made possible by great improvements in search engine technology, the task of finding information contained within these blogs has become so easy, easier than I could have ever imagined as a teenager in the 80's. I think back to my days in elementary school and middle school and how I used to research and write my school reports and projects. Back then, all the information I needed was in a 20 volume set encyclopedia. If it wasn't in there my next option was the school or local library. These were and still are great resources for formally publish information. I wish to give a little back where I can.

Now when it comes to writing, I am not very good. As you read this I'm sure you are letting out a little chuckle while at the same time thinking to yourself, "no kidding". Good writing is so much rarer than it should be. For some people, writing comes so easily and for others it takes more of an effort, more than I wish at least. The great thing about blogs is that they are informal. There is so much good information available by people who are subject matter experts, but not necessarily great at writing. The chances of most people ever publishing a paper on a subject they might happen to be knowledgeable about, was once very slim to none. Today, anyone can share their thoughts and opinions in minutes.

You will hear much more from me about me, my business, my projects, tips, and tricks of the trade; right here on my blog…