Excluding files from C++-Projects will delete them from source-control, also - by max berghammer

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 636116 Comments
Status Closed Workarounds
Type Bug Repros 8
Opened 1/14/2011 4:34:18 AM
Access Restriction Public


Everytime i remove a file from an unmanaged c++-project in solution explorer, either through the "Del"-key, the "remove"-command in context-menu or the "exclude from project"-command in context-menu, a pending delete will be filed in source control (TFS2010, in our case), too.
If i undo the pending delete from the pending-changes tool-window, the delete will be undone, but the file will be added to the project again, too.
This is really annoying, as we have .cpp- and .h-files that are being used in multiple projects being not in the same solution.
Sign in to post a comment.
Posted by John Boncek on 6/6/2012 at 8:28 AM
Still broken in VS 2010, SP1.
Posted by Microsoft on 3/15/2011 at 5:51 PM
This is one of the issues that we are looking into fixing in the next product cycle. This is a dupe of an internal bug that we are using to track the issue - thus the lack of activity on this bug. We will update this thread once there is progress.
Posted by max berghammer on 2/22/2011 at 1:48 AM
And now? May we have a status-update on this incident, please? I attached a vid to this, additionally i attached a link to a vid residing on an external resource, too -> there's nothing more, i can do for you.

This bug appears in SP1-Beta, also! May we have a chance of this getting fixed in SP1?

I'm really frustrated about this, as you promised VS2010 to be the "new VS6" for VC++-Developers, and what we got is total crap: It is slow, it uses loads of memory and the most primitive things don't work anymore, as this issue proves...

I'm sorry, but if SP1 doesn't fix at least this bug in VS2010, we'll simply stay with VS2008, as it makes VS2010 absolutely unusable for everyone in our team. (20 developers) It is absolutely contra-productive, to switch to windows explorer to undo wrongfully deleted files and then switch back to VS2010 during development. I'm really fed up writing macros/addins/packages/whatever fixing all the problems we are experiencing within VS...
Posted by max berghammer on 1/17/2011 at 1:49 AM
Thanks for your reply !
I added a link to the "Steps to reproduce"-Section. Is this ok for you ?
Posted by Microsoft on 1/16/2011 at 8:12 PM

Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Could you please attach a video file to this feedback through our site to help us reproduce the issue?

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by ndee on 1/14/2011 at 5:15 AM
We stepped back to VS 2008 - we cannot work with this!
Posted by ndee42 on 1/14/2011 at 5:11 AM
It is amazing how Microsoft could release this!!!
Everybody who has a public library will face this issue.
Please fix this in the next ServicePack!
Posted by Microsoft on 1/14/2011 at 4:58 AM
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)