Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

A few of my friends have noticed some quirks with vs2010... notably the Undo/Redo feature doesn't seem to work reliably... often messing up the code beyond comprehension.

What other quirks have you seen?

Update for vs2010 users (non SP1)

Please post your bugs at Microsoft connect, and a corresponding link here so we can up vote them as needed.

https://connect.microsoft.com/VisualStudio?wa=wsignin1.0

Update for VS2010 SP1 Users

You can download the SP1 for all versions of Visual Studio here. Just be aware that there are compatibility issues mentioned in the readme. Also some people have reported issues with this release.

Please report bugs here: https://connect.microsoft.com/VisualStudio?wa=wsignin1.0

share|improve this question
show 1 more comment

closed as not constructive by Mark Trapp Jan 3 '12 at 19:25

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

18 Answers

up vote 12 down vote accepted

The Add Reference diagram still sucks. It just sucks in new and different ways from 2008. It is better now that you can get to the Recent, Browse, and Project tabs quicker. However, the tab that shows the huge list of assemblies is not very useful. It loads in dribs and drabs, but with no indication of when it is done or not, and with seemingly no rhyme or reason to what is being loaded. It doesn't seem to sort correctly if you click on one of the columns. And it is still slow to actually have the list fully populate. And although you can type in the start of an assembly name, and it will go to that item, it is not obvious that you can do this, and you can't see what you are typing so it is easy to misspell and not find what you are looking for.

share|improve this answer
1  
try the Productivity Power Tools extension visualstudiogallery.msdn.microsoft.com/… –  hiena Feb 2 '11 at 11:48
1  
Yeah, definitely use at least the new add references dialog from there. Other stuff can be optional, but that new dialog is what it should have been at release, or at least included by default now. –  Rangoric Feb 2 '11 at 14:50
add comment

I haven't used it much yet (I have it at home, but still using 2008 at work.) So far so good, but the new help system is garbage compared to what it was before (if you've used both, you know what I mean.) That's been a real productivity killer for me - I usually gave up and just went looking on the web for answer (that's fine at home, but at work we're on an internal network with no direct Internet access.) Some people have come up with alternatives, but they are rather slow and don't work very well.

I don't recall having problems with undo though. That's an odd one.

share|improve this answer
add comment

CTRL+UP does not scroll the view window in code editor, instead activating class drop down box. Even worse, I don't find a way to customize it.

share|improve this answer
show 2 more comments

I've been using VS2010 for C++ development for a few months on a Windows XP machine. It is noticeably slower than VS2008, which may be caused by the more sophisticated intellisense, which I have turned on. Or it may be the fact that it is written using WPF.

It freezes a lot, and crashes once a day on average. And on top of that, the more sophisticated intellisense often goofs, and reports errors that are not there. I suppose it doesn't always catch the fact that a header file has been modified.

I hope there is a service pack coming, which will fix these bugs. However there are also a couple of issues that really bother me, and seem unlikely to be fixed. One is the lack of emacs key bindings, and the other is the fact that the built in unit test system requires the use of managed code.

Here's another one. The "Project Dependencies" menu no longer seems to do anything. To specify which projects depend on which "Project References" in the property sheet are used. It is a complete mystery to me why the "Project Dependencies" menu is still there or what it does.

Edit:

I have just got a new faster machine with Windows 7. VisualStudio does not crash or freeze any more. Works like a charm. Very fast and responsive.

share|improve this answer
show 4 more comments

Batch build is fundamentally broken for solutions containing dependent C++ projects. I have a project which builds 32 and 64 bit configurations, release and debug.

With Visual Studio 2008 I used to test a full clean build with batch build because switching to each configuration in turn was a pain; with Visual Studio 2010 this fails as it sometimes uses the currently selected configuration to link against instead of the currently being built configuration resulting in 'incompatible object file format' errors at link time.

It's a known bug, but very irritating.

Microsoft, in their infinite wisdom, have decided not to fix this problem.

https://connect.microsoft.com/VisualStudio/feedback/details/554339/visual-studio-2010-bug-in-platformname-handling-in-batch-build

https://connect.microsoft.com/VisualStudio/feedback/details/556158/batch-build-links-to-wrong-referenced-projects

share|improve this answer
add comment

I've found a number of issues:

  • It's memory hungry and prone to leaking. Over the last couple of weeks I've been converting a set of Silverlight projects to .NET 4 and Silverlight 4 and when compiling several times over a short period it would either generate out of memory errors or just fail.

  • It's also prone to crashing out, apparently at random when compiling. This could be related to the "memory" issues.

  • It takes a long time before you can edit when switching windows. This is particularly true of xaml files. The code window doesn't recognise keystrokes so you can't double click to highlight a word and then type to replace it.

  • The XAML error display at design time is still not perfect. I'd make an edit (changing a reference to an assembly) and the code would appear to be OK, but on compiling it would generate errors. These errors would then be highlighted in the code window.

  • Compiling is slower than VS2008 and it seems to recompile code that hasn't been changed. I'd do Ctrl+Shift+B to compile (because I wasn't 100% sure I'd got all the errors sorted) then when that succeeded do F5 to run the application - it would often recompile the code again before executing.

I'm hoping that there is an update soon before we roll VS2010 out across the team - otherwise we're going to have complaints.

Now I'm running on Windows XP SP3 with .NET 4 and SL 4 installed rather than Windows 7, so I don't know whether that has any bearing on the situation.

UPDATE:

  • A test on Windows 7 showed broadly similar build times, so it looks like the operating system doesn't matter.

  • There's a registry entry you can set to disable Live IntelliSense for RIA Serivces (as described here on the Silverlight Forums). Doing this seems to speed up the build times and improve the switching between windows. It's still not perfect though.

share|improve this answer
show 2 more comments

As ChrisF noted, VS2010 is memory hungry and leaks at times. I'm actually battling with IT to ramp up our PCs to account for how hungry it is. If I have multiple instances of it open along with the other development tools I use, I've actually ran out of memory and nearly max'ed my page file to the point in which my PC crashes or freezes up.

The mouse scroll problems are annoying as well. I've noticed that it's a driver problem along with being a bug within VS2010, but coming from VS 2005/2008, it's hard not to be used to using the mouse wheel to scroll through windows. Sometimes it works, but most of the time... it's hung up on the Solution Explorer.

I've had constant problems with VS2010 hanging up the web server instance as well, taking 50% of the CPU and not allowing me to end it. Once I end the process in Task Manager, VS2010 is frozen and I have to end it as a process as well and restart. I've had this happen a few times consecutively, maybe 5 or 6 times.

share|improve this answer
show 1 more comment

I use Ctrl + . to bring up the smart menu all the time - the menu you can get to when you see a little rectangle pop up underneath some symbol you just typed that lets you do things like automatically include the namespace of the class you're trying to use, or automatically implement all the methods of an interface. Because of the way VS2010 does background compilation, it takes 1/2 to 3/4 of a second for it to parse the entire symbol name.

I'm pretty fast with Ctrl + ., so sometimes I'll do something like jam out MyClass : IMyInterface, immediately Ctrl + ., and then hit enter to automatically implement IMyInterface. What happens? Well, the parser only got through IMyIn, and the default menu selection upon hitting Ctrl + . for a class that VS doesn't recognize is to implement it in your project, so now I get a brief progress bar and a new IMyIn class in my project.

share|improve this answer
add comment

I can upgrade my memory, to curb it's hunger for memory. I can use an SSD to curb it's hunger for disks. But, what do I do for it's absolute abuse / misuse of the CPU for all things important? The IDE refuses to use multiple CPUs on multi-core hosts (i.e., all hosts, these days). It does this after all the hype MS is putting into writing multi-processor efficient code and all of the tools they are providing to "help" developers do this.

I appreciate the new user-interface, but add extensions (Visual Assist, Resharper, whatever) and thing crawls. What sane developer develops without extensions, these days?

To summarize: We can live with it being a memory hog, but MS, please speed the thing up and have it use all available cores efficiently.

share|improve this answer
show 1 more comment

Opening big workflow xaml files like the one provided for team build and working with it is almost impossible. On XP it will crash after using a lot of memory.

share|improve this answer
add comment

A C++-specific answer...

The biggest problem I've had with it so far is that, when importing a project from VS2008, because I have in my source files:

using namespace std;
using namespace boost;

and I'm using boost::shared_ptr<>, it's getting confused about which namespace an unadorned shared_ptr<> comes from even though I've never #included the std::shared_ptr<> header.

share|improve this answer
show 2 more comments

We've had problems with the debugger. It'll ignore breakpoints, and other times break randomly. If you restart, it'll work properly for one session, but then it's hit or miss.

share|improve this answer
add comment

Publishing from VS2010 to my website works very well but causes problems with my service provider's wireless modem. After two or three "publishes", my network goes down and I have to reboot the service provider's modem and my router.

share|improve this answer
add comment

Switching Source Control plugins is a hassle.

Let's say I switch back and forth between projects in Team Foundation Server, GIT, SVN, etc. Each time I do, I have to go into the options of VS and change the plugin I use to access source control. It's like Visual Studio can only keep track of one type of repo at a time. It'd be great to be able to not care, or at least have all the options in the toolbar without having to totally swap them out every time.

share|improve this answer
add comment

Something I've noticed is that the first time during a session, I delete any item in the solution explorer, the whole of VS will freeze for about 1 minute and then resume as normal. Any subsequent deletions work fine. But this is happens to me all the time.

share|improve this answer
add comment

In the little "find" textbox at the top of the screen on the standard toolbar (the one where you type in text to find it on the page) it tries to do autocomplete from previous entries, which I think is new. It's not a bad idea in theory but they insist on trying to match your text to previous text entries, often times with different capitalizations, and then when you type what you really meant anyway the letters that were capitalized from the mismatched word stay there, which is really annoying when you're trying to do a case sensitive search.

That and I'm not digging the blue theme. Otherwise it's a great IDE.

share|improve this answer
add comment

I have horrible graphics artifacting with VS2010. It'll be working fine, and then I switch over to another tab, and the code screen is rendered a black and grey pattern. Obviously extremely annoying, to the point where it's difficult to get any work done.

I should note that this only started happening after install Windows 7 SP1, and that reinstalling VS and/or the graphics drivers hasn't helped any. I will probably be reinstalling Windows 7 this weekend to try to fix this issue.

share|improve this answer
add comment

I'm having trouble with window management.

I'd love it if Sara Ford (or somebody of her ilk) could tell me if I've identified a legitimate usability problem (or bug) or if I'm just not "doing it right".

In a nutshell, when I navigate between the text editor, 'Solution Explorer', 'Team Explorer', 'Test Editor', and the debug windows, my windows tend to increase/decrease in size; and if it's often difficult to revert to my previous window arrangement without selecting 'Windows > Reset Window Layout'.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.