Deletion of projects may delete files in another project by ldmitry

Of course, with software, there is ALWAYS a possibility of a bug :). That said, from the greatly differing behaviors of tfsdeleteproject and deleting a group of files in a checkin I am VERY confident that these are unrelated. It does not however mean that your developer didn't hit another issue that is causing confusion here. I'd love to hear more about what the developer was doing and what they expected to happen versus what actually happened. Let's start with changeset 187. Did the developer attempt to check in any changes around the time that changeset 187 was created? If so, what changes did they think they were submitting and what was the workflow they used to create and submit those changes?

Furthermore, if you need the files that were deleted back, you can always rollback changeset 187. Let me know if you need directions on how to do this.

Thanks,
Taylor

Taylor, are you sure, that destoy of project A can not accidentially delete files in project B at next commit? Is it by design impossible?

You know, it mean, that my developer have deleted files, not software bug.

P.S. Who should i trust - the guy sitting 10 meters from me, or 10 000 kilometers? ;-)

Thanks for the feedback. I took a look at the log files and I think there may be a misunderstanding of the way that TFS works. tfsdeleteproject.exe will *destroy* an entire team project and all of its contents. Destroy is much different than delete. Destroy makes it look like the files destroyed were never present in the system. Delete leaves the history and contents of those files around in case you want them back.

Now, let's talk about delete. In order to delete a file foo.cs in TFS you will first pend a delete on foo.cs and then you will check-in that delete. This works the same way as an edit where you would pend an edit and then check-in that edit. I took a look at the changeset 187 mentioned in your bug. It appears that the developer pended deletes on all of those items and then checked them in.

I am closing this as by design because that is what our logs show as well. If you still have questions, feel free to respond and we'll be happy to answer them and dig in more if needed.

Thanks,
Taylor
TFS Version Control

Thanks for your reply. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

If i will try to reproduce, i am worry if i could loose some work on my TFS account. It mean - i need another accouint to try to reproduce, and not sure it will be reproduced (because you have tried).

I think some unregistered by me conditions are lost. I described estimated reproduction steps, not sure steps, because incident happen only once. I have wrote steps by guess - only history is true.

I think more productive would be fact fixation. May you look for TFS request logs (at low level) at 14.02.2013 and say, if change 187 was for delete or for check-in of changed files?

Hi ldmitry,

We are unable to reproduce the issue with the steps you provided. Could you please collect some steps while you're repro'ing the issue?

Thanks,
Microsoft Visual Studio Connect Support Team

Ok, you explained me what feedback tool can do. What information should i submit within 4 business days?

Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please use the feedback tool to the collect steps while you're repro'ing the issue?

Visual Studio now has an extension called Microsoft Visual Studio 2012 Feedback Tool, available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1. upload files,
2. collect trace and dump files
3. collect steps while you're repro'ing the issue, as well as
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team

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)