A bug in Visual Studio (vs2010 and earlier, probably with vs2012 also) - by namtad

Status : 


Sign in
to vote
ID 779272 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/14/2013 9:38:13 PM
Access Restriction Public


I've noticed this problem in Visual Studio 2010 and earlier versions and I would not be surprised that this problem exists in the latest version.  The problem is the editing of the project configuration settings (e.g., "Debug", "Release" and so on that can be added or removed at

   Menu > Build > Configuration Manager...

The problem I noticed was that when you remove an item or two (at the <Edit...> section of the
listbox labeled "Active solution configuration"), it will be gone from the solution list on the toolbar.  However, the "deleted" configuration somehow continue to bother me in "Batch Build" section. 

Today, I finally found the solution (which I guess should work but needs some more work to verify my new trick really solved the problem).  

I've prepared a longer text to discuss this problem (how to create the problem) and solution.
I hope you guys can fix this problem.  I've been living with extra configurations that I did not want but I could not figure out how to eliminate the unwanted items in the configurations.  As a consequence, my batch-build sequence (which takes about 10 minutes each) wasted a few more minutes every time I did that (so, over the years, I've wasted many tens of hours waiting for the unnecessary build --- all because of the bug in Visual Studio.  Now, I hope I can do it right by knowing how to remove the extra configurations and also telling you how to reproduce this problem and you can fix the Visual Studio bug at the source.  Thank you for your attention.

(I'm pasting the entire report that I prepared at the "Steps to reproduce" section below.)

Kan Yabumoto


Sign in to post a comment.
Posted by Microsoft on 2/28/2013 at 2:31 PM
Thank you for your feedback. We have investigated this issue and determined that it is not a regression from previous versions of Visual Studio. As this issue is not a regression we will consider it in planning for future versions of Visual Studio if we receive a significant volume of customer feedback pertaining to the issue.
Posted by Microsoft on 2/19/2013 at 7:02 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/14/2013 at 9:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)