Does anyone know how to do this?
I can't tell you how many times I've done this by accident and can't undo :mad:
Printable View
Does anyone know how to do this?
I can't tell you how many times I've done this by accident and can't undo :mad:
Hey,
Doesn't look like there is a way to do this, or that it will be changed any time soon.
A quick google seemed to confirm this:
http://social.microsoft.com/Forums/e...2-de3ac5fd5ac1
https://connect.microsoft.com/Visual...dbackID=110852
Not the answer you were looking for.
Gary
you can use this plugin to do avoid accidental drag and drop in solution explorer: http://visualstudiogallery.msdn.micr...0-6a2882120acf
Hey,
That is a nice find. Bear in mind though, that add in will only work with Visual Studio 2010.
Gary
Yep, I was already using it but totally forgot about this thread :)
Two of my other favorites I found in the online gallery are DevExpress Tools and Productivity Power Tools. I didn't find VS2010 that much more useful than VS2008 until I found these extensions ;)
Really!!
I would have thought the speed improvements alone would have been more than enough reason to move to 2010.
Gary
That's partly true but I don't notice much of a difference my machine is so slow anyway.Quote:
Originally Posted by gep13
I think quad core xeons are next for developers so I'll be happy soon ;)
Ha ha, I know that feeling only too well!!Quote:
Originally Posted by wey97
Fingers crossed!!Quote:
Originally Posted by wey97
so how many of you are actually staying with VS2008 and not moving to vs2010? were I work we have few projects that no one wants to risk upgrading, but all new development is in vs2010.
When you say risk upgrading, what do you actually mean?
Assuming you are targetting .Net 2.0 or later, then there is nothing to stop you continuing to target this version of the Framework within Visual Studio 2010.
We will be moving to Visual Studio 2010 shortly within my company.
Gary
I said it in a wrong way, most developers want to upgrade, but managers and few more senior devs don't want to risk because, apparently, they have bad experiences with upgrades in the past..
If I were you, I would take a copy of the code base, put it somewhere completely different on your computer, then open it up in Visual Studio 2010, and show them there is nothing to worry about :)