As with any major release, the release of Visual Studio 2010 SP1 is likely to raise questions about compatibility with existing releases, particularly the out-of-band and pre-release copies of our products. The Visual Studio SP1 team has done a lot of...

Over the past several years, the Visual Studio team has been actively working on ways to hear from you (our customer) and continue to improve our developer tools and frameworks. The Developer Division even built an entire portal (Microsoft Connect ) exclusively...

Your feedback is important to us. Please take 5 minutes - link to the survey and let us know what you think. Visual Studio 2010 Service Pack 1 Beta Survey Thanks!

We are pleased to declare that Visual Studio 2010 Service Pack 1 Beta and the .NET Framework 4 KB2162169 Beta will be supported as a “go live” release. This means that this software has met high standards of quality for a pre-release, and...

It's been a few months since we've shipped Visual Studio 2010. We would like to hear what you think so far. Your feedback will help inform the next versions of our products. We do not collect identifying information such as your name, email or IP address...

Visual Studio 2005 Beta 2 will be releasing soon and with many customer bug fixes and suggestions incorporated. Hundreds of bugs were fixed only because they were found and reported by customers. We've fixed about 75% of the fixable customer reported...

This week's "Eagle Eye" Bug of the Week Award goes to MSDN Product Feedback Center user “JoeF ” for the bug: Arithmetic operation resulted in an overflow with Int32 This is an interesting hard to find bug. The CLR team is looking at fixing this...

This week's Bug of the Week Award goes to MSDN Product Feedback Center user “Pasi Heinonen ” for the bug: Circular base class dependancy crash the Visual Studio From Cyrus Najmabadi, Software Design Engineer on the C# team: "Interesting bug. As one might...

This week's Bug of the Week Award goes to MSDN Product Feedback Center user “PGomersall ” for the bug: Starting MS Outlook 2003 starts C# Express installer Thanks for helping make Visual Studio a better product and keep the great feedback coming! Marie...

This week's Bug of the Week Award goes to MSDN Product Feedback Center user “Marina ” for the bug: Designer not generating correct code - code cannot compile. We appreciatey your persistance on this issue and the effort made in getting us the attachment...

The Suggestion of the Week Award goes to MSDN Product Feedback Center user “Mike Taulty ” for the suggestion: RSS Feed for Top Rated Bugs Thanks for helping make Visual Studio a better product and keep the great feedback coming! Marie Hagman Visual Studio...

Last Friday's Bug of the Week Award goes to MSDN Product Feedback Center user “JDM ” for the bug: Right shift of a literal int produces logical instead of arithmetic shift Thanks for helping make Visual Studio a better product and keep the great feedback...

Recently I opened a discussion on the Microsoft responses to issues posted in the PFC. One question we’ve been grappling with that’s related is how to resolve bugs that repro on the original build the customer reported the issue for, but on our latest...

Ask and you shall receive! I've been thinking about a Suggestion of the Week since we started the Bug of the Week award because I run across so many great suggestions when hunting for bugs to award. So this week, I'd like to award the first Suggestion...

This weeks Bug of the Week Award goes to MSDN Product Feedback Center user “Jouko Kynsijärvi ” for the bug: Button renders text & focus rectangle inconsistently compared to native Win32 button Thanks for helping make Visual Studio a better product...

This weeks Bug of the Week “Most Votes” Award goes to MSDN Product Feedback Center user “Scott Hanselman” for the bug he posted: Tray Icon support is limited: System.Windows.Forms.NotifyIcon doesn't support Balloon Help without P/Invoke This bug currently...

This weeks Bug of the Week Award goes to MSDN Product Feedback Center user “Paul D. Murphy ” for the bug: The 1! in the end of filename causes debugger not to hit breakpoints Thanks for helping make Visual Studio a better product and keep the great feedback...

This weeks Bug of the Week Award goes to MSDN Product Feedback Center user “Kevin Dente” for the bug: Adding Web Reference from Visual Studio generates fields instead of properties This bug was originally resolved as "Won't Fix" but was fixed after Kevin...

This weeks Bug of the Week Award goes to MSDN Product Feedback Center user “FransBouma” for the bug: Cursor doesn't remember indentation after enter is pressed This is a good catch that our internal testers may have never found but is important for the...

We would like to add a mechanism on the PFC by which customers could rate each Microsoft response they receive to issues they file. In the meanwhile, here are some ideas on what I think we should strive for in terms of response quality. With each response...

This weeks Bug of the Week “Eagle Eye” Award goes to MSDN Product Feedback Center user “TAG” for the bug: IDE does not colorize single character classnames if they follow immediately after closing "}" This is a narrow case our internal testing did not...

Josh Ledgard wrote a great 4 part series on transparency and implications for customers and corporations. The PFC is an excellent study of the points on benefits and fears associated with increased transparency. The PFC by nature exposes all the problems...

This weeks Bug of the Week “Most Votes” Award goes to MSDN Product Feedback Center user “kzu” for the bug he posted: Where did components area on Web Forms go?? This bug currently has 152 votes - the most of any bug submitted so far (note this is out...

In recognition and appreciation for helping make Visual Studio 2005 (Whidbey) an even better product, today we’re kicking off the first Bug of the Week Award! Keep the awesome feedback coming and you too may be a winner. This weeks Bug of the Week “Eagle...

It’s simple, we let the customers tell us the priority of the issue. We’re basing the priority value on the customer average rating and number of votes. Here’s an example: Priority 1: Average vote value is 4.5 or higher and 6 or more people have voted...