It is so frustrating; drag a file in the solution explorer to another folder in the solution explorer, and Visual Studio.NET 2005 may check out all the datasets in the destination (if there are any) and regenerate them again.
For some stupid reason, that only a developer at Microsoft can put in that VS.NET 2005, the drag and drop operations do trigger the custom tool of each dataset to regenerate everything everywhere!!!!!
And we have our own custom tools, and they are triggered too.
You know, whoever wrote that solution explorer in VS.NET 2005, man, if you don’t know how to code a drag and drop, maybe you should not be a developer at all, forget about not a developer at Microsoft; maybe you should look for something else not related to the PC’s at all!
Now, everything is checked out, in a large project, to solve my problems is to undo the check out of everything and write that part again, or spend 2 hours trying to figure out what was regenerated by that idiotic bug, and what I did change.
I’ve submitted this more than a year ago, with a video recording of the screen too, and it is reproducible on every machine, and if you are using a tablet pc with a pen, that bug is there by default, and nothing done by Microsoft.
So stupid, I guess it is a one minute fix, and it would have solved so much, I am suffering from that issue every day, from the day VS.NET 2005 was release until today, it is like having a broken tooth and trying to avoid eating on it, so frustrating.
But who cares, a bug of the billion bugs in the list of things to fix in VS.NET.
Visual Studio .NET 2005 lost my work, again for the 100 time
bishoycom
It was there for more than a year, nothing done, and then closed
Keena
Check http://connect.microsoft.com/VisualStudio/feedback/ to see if your issue has already been sent to Microsoft. If not, create a new issue posting the steps to reproduce it, then post a link to that issue here. That way anyone who thinks this issue is important or is having the same issue can vote on it and provide feedback.
They tend to put a higher priority on issues logged on connect.microsoft.com that have many votes.
Ron Luebke