Received a follow-up from Microsoft regarding <a href="http://lakario.blogspot.com/2009/07/visual-studio-2008-var-keyword-bug.html">Visual Studio var Keyword Bug</a>. Here's what Microsoft support had to say about the issue.

Alright, my previous post was lot of ranting… I have to make it up. I hate ranting because it never bring any solutions, only problems. When someone is building a software, bugs will happen as true as the sun rise everyday. Sometimes it will be simple change request but there will be bug that are go...

I was writing acceptance test for project today and I needed to include a file inside my Excel 2007 sheet. After fiddling around a little, I found “Insert Object”. This allowed me to insert a file and have it available to anyone opening the Excel 2007 document. When I dragged and dropped the file to...

Be careful when using LINQ. If an application is using LINQ to SQL and the queries involve the use of strings that can be highly variable in length, the SQL Server procedure cache will become bloated with one version of the query for every possible string length

So you install Commerce Server 2007 and are ready for the money and SEO to start flowing. Next thing you know. Google ignores you completely. What do you do? more...

If use the default Split Container to build a Windows Form or create a new user control, and set some properties of that Split Container at design time using Visual Studio 2008, you may end up with a broken form or user control. I got that error using the Visual Studio 2008 - Professional Edition.

Using WiX 3.0 in Visual Studio? Don't add subfolders to your project or you'll spend a day figuring out why your work is E_FAILing

This little hack shows how to overcome little bug in Asp.Net Ajax Control Toolkit Rating Control that causes focus to jump to the top of page when user clicks on the control to rate some content.

Weird bug made it necessary for me to remove PowerCommands for the time being =\

We found the first bug listed here at work as well.

User Comment: "If I read this right, this is a catasrophe, isn't it? No one can safely deploy the 3.5 framework with their applications without adding this custom code to their installer?"

By now you've probably seen a lot of the brouhaha over a bug in the newest version of Excel, 2007. Basically, multiplying 77.1*850, which should give you 65,535, was actually displaying 100,000.

Here is why you should make sure your parameter names are consistent between your declarations and definitions in C++. Not doing so leads to strange and confusing behavior in the debugger.

The author shows a flaw in String.IsNullOrEmpty of the .NET 2.0. Microsoft replies that this bug won't be fixed until Orcas. (see bug report at: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=113102 )