Visual Studio '11' Announced

Re:Visual Studio '11' Announced by bwarp on Thursday February 23, 2012 @04:15PM (#3626802)

Sure it looks all pretty, but have they made it faster and more reliable?

VS2010 is just damn slow and falls over on me at least 2-3 times a day which is not acceptable. When you pay for 25 VS2010 premium licenses with MSDN on top of your gold partner allowance, you expect it to work.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by MartinCron on Thursday February 23, 2012 @04:53PM (#3626962)

VS2010 is just damn slow and falls over on me at least 2-3 times a day which is not acceptable.

Non-aggressive suggestion: think you've got something screwy with your system, I've had VS Fall over on my 2-3 times in the last several years of heavy use. It doesn't have to be that unstable. Also, with an SSD and enough RAM, I don't feel like I'm ever waiting on VS anymore.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by elemeno on Thursday February 23, 2012 @05:11PM (#3627040)

I'd second that. In the past five years (or at least since VS 2008), I can remember VS crashing on me maybe half a dozen times. That's with spending most of my time working on pretty large multi language projects.

For context, I don't use any extensions other than (sometimes) ReSharper and Tortoise svn/git/hg.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by brunomlopes on Thursday February 23, 2012 @06:50PM (#3627317)

Mine doesn't crash on Web projects, but can't work for a couple of hours on a Windows Phone 7 project without it going boom.

I think most of it works fine and dandy, but some parts can be quite sensitive.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by MartinCron on Thursday February 23, 2012 @07:47PM (#3627455)

Fair enough, I haven't worked on any Windows Phone 7 stuff yet, so it may be fatally brittle there.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by bwarp on Friday February 24, 2012 @03:15AM (#3628427)

I've dumped all extensions - I had R# and VisualSVN.

The solution does have about 80,000 files though.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by wr1472 on Friday February 24, 2012 @10:05AM (#3629370)

Maybe VS crashing is the symptom, and you should look for the cause around the fact that your solution has 80,000 files within it?

[ Parent | on HN ]

Re:Visual Studio '11' Announced by georgieporgie on Friday February 24, 2012 @12:48AM (#3628171)

I do C++ work. VS2010 is so slow and crashes so often for me that I abandoned it (and, sadly, its limited C++0x support) for VS2008. This is on a Core2Duo, 8G RAM, a hybrid hard drive, and accelerated graphics.

I was pretty happy with VS2008 until the other day, when I found that I can reliably crash it by opening a particular XML file. sigh

[ Parent | on HN ]

Re:Visual Studio '11' Announced by coffeeaddicted on Thursday February 23, 2012 @05:33PM (#3627120)

Speed is fine here and I generally enjoy working with VS 10 when I'm on Windows (showing errors while typing is a fantastic feature which I haven's seen for c++ before VS10). But my annoying VS 10 bug is that approximately once per week it simply refuses rebuilding a changed c++ file until I clean and rebuild the whole project. It just continues using the old object file despite having c++ files with a newer date - and what makes this really annoying is that this is a bug you certainly only notice after a while when results just stop making sense. Others in the project have the same trouble - maybe we messed up some setting, but we haven't found any setting yet about simply ignoring source-changes...

[ Parent | on HN ]

Re:Visual Studio '11' Announced by jerhewet on Friday February 24, 2012 @09:00AM (#3629177)

Try adding a semicolon in your source files immediately after your includes:

#include "stdio.h" #include "system.h"

;

int StartOfYourCPPCode() {

There's a long-standing bug with pre-compiled headers and code regeneration that (apparently) Microsoft has never fixed. There were (still are?) so many obscure issues with PCH that I just disabled it altogether.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by coffeeaddicted on Friday February 24, 2012 @12:44PM (#3630062)

Thanks. We also had suspected pre-compiled headers and also just disabled them completely, but unfortunately that wasn't it. I'll try adding a semicolon next time it happens to check if that changes something.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by pseale on Friday February 24, 2012 @03:05PM (#3630763)

I blame XAML, and I'm justified. Some of my teammates here have changed Visual Studio to open XAML files with the XML editor, which means * Visual Studio no longer crashes all the time, and * they lose all XAML intellisense.

I choose to keep the XAML editor for its usefulness, but I run Task Manager (well, Process Explorer) open in the tray at all times to monitor my CPU. If your CPU spikes while you're doing nothing, it's a good sign that Visual Studio may crash.

And as everyone else says, it's rock-solid while doing web development or anything not involving XAML.

[ Parent | on HN ]

Re:Visual Studio '11' Announced by eatporktoo on Thursday February 23, 2012 @04:59PM (#3626986)

Do you use a lot of extensions? I have it crash about that much as well. I wonder if we compared extensions if we could pin point which one is causes the crashes.

[ Parent | on HN ]