Why does Visual Studio just not work ?
-
I have some code in my application start, for an ASP.NET web site. I was running it with breakpoints, and suddenly, the breakpoints stopped working. So, I closed VS and reopened. It's frozen on trying to open my website, I think I need to reboot.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
I have some code in my application start, for an ASP.NET web site. I was running it with breakpoints, and suddenly, the breakpoints stopped working. So, I closed VS and reopened. It's frozen on trying to open my website, I think I need to reboot.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
I have some code in my application start, for an ASP.NET web site. I was running it with breakpoints, and suddenly, the breakpoints stopped working. So, I closed VS and reopened. It's frozen on trying to open my website, I think I need to reboot.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Just plain broken. Ask VS to Find Definition of a function sitting a few lines above in same source file? (a) Nope, doesn't exist (b) Here is a list of 67 places a function of that name exists in the Solution - please pick one. (c) Occasionally, it will take you where you want And also, it can take over a minute to work this out. Ask VS to Find Declaration of the function definition you're sitting on? Most of the time, it grinds away for a minute only to sink back exhausted on the definition again. Build? If you're lucky! (a) Sometimes it actually identifies all the changed source and recompiles those objects - yay! (b) Often it misses some changed source and does not recompile the objects - yes, those projects are ticked as dependencies of the executable :-( (c) Quite often the incremental linker loses the plot and generates a corrupt binary. No kidding - I've changed one line in a method of a class in a .cpp file with not a template in sight, clicked build and then run it ... Crash! Ordinal 99 not found in ThirdParty.dll (or access violation indexing into std::vector is an old favourite) Sigh ... Rebuild ... Run ... Crash! Ordinal 99 etc. Grrrr ... Manually delete all the output object files, intermediate linker files, executable, etc. Build ... Run ... Works now (phew). VS2008 SP1 was a bit quirky but Vs2010 lives in a full-blown psychotic episode.
-
In answer to the specific question of the title, I suspect this is because Microsoft developers rush product out the door due to the marketeers - whether it is fully tested or not. I have problems with VS2010 at least once a day - and I am not a particularly heavy user (although my dietitian would argue the case!) A particularly annoying aspect is when an unhandled exception is raised, with the nice little alert box showing the message, with a line pointing to the line of code throwing the exception? Almost every time I get this, the screen corrupts, so I cannot see the line properly - sometimes moving it from one monitor to the other corrects the fault, sometimes restarting VS (a royal pain in the middle of debugging) and sometimes I just go home.. I have had breakpoints effectively stop working before, too. so, little comfort though it may be, you're not alone...
___________________________________________ .\\axxx (That's an 'M')
I use VS for at least 5 hours every day, and never ever have these problems. Mine runs as smooth as silk. But I run 64 bit Vista, with 8Gb of ram. Perhaps that is what is rendering it stable?
-
If using VS2010 - that's your problem. It's a well known fact that you should never use any version of VS until at least the second service pack! Note There is a difference in terminology with providers A Google Beta release means its a release version A Microsoft release means its a Beta version :) Has Google ever actually released anything that isn't a Beta ?
Utter cobblers.
-
Utter cobblers.
-
I use VS for at least 5 hours every day, and never ever have these problems. Mine runs as smooth as silk. But I run 64 bit Vista, with 8Gb of ram. Perhaps that is what is rendering it stable?
Michael K Gray wrote:
I use VS for at least 5 hours every day, and never ever have these problems. Mine runs as smooth as silk. But I run 64 bit Vista, with 8Gb of ram. Perhaps that is what is rendering it stable?
I use VS2008 sometimes 12 hours in a day - can't think of more than once or twice in a couple of years where the IDE crashed or became unstable. I use it on my own equipment (64-bit W7, 32-bit W7) using VSS and on the office machine (32-bit W7 using TFS). Never have any problems with it. I don't do much web development but have done some and it runs stable, no problems. Sorry to hear people are having trouble with it. Glad I ain't among them! -Max
-
That's gold.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
I think you need to cover your office floor, walls and ceiling with tin foil... You need to rule out the induced-electrical-flow-from-flowing-water syndrome possibility... To be on the safe side, you should wrap yourself with tin foil... This will rule out the jynx effect...
-
Michael K Gray wrote:
I use VS for at least 5 hours every day, and never ever have these problems. Mine runs as smooth as silk. But I run 64 bit Vista, with 8Gb of ram. Perhaps that is what is rendering it stable?
I use VS2008 sometimes 12 hours in a day - can't think of more than once or twice in a couple of years where the IDE crashed or became unstable. I use it on my own equipment (64-bit W7, 32-bit W7) using VSS and on the office machine (32-bit W7 using TFS). Never have any problems with it. I don't do much web development but have done some and it runs stable, no problems. Sorry to hear people are having trouble with it. Glad I ain't among them! -Max
We have sevarl machines at work with VS2010 installed on Windows XP Pro. SP3. The machines with weaker graphics cards exhibit these types of problems. So based on that our educated guess is that the problem is with WPF Rendering (VS2010 UI was rebuilt in WPF) on these weaker machines is what gets stuck. Never saw a problem running VS2010 on Windows 7. Time to upgrade the OS ... --- Adar Wesley
-
We have sevarl machines at work with VS2010 installed on Windows XP Pro. SP3. The machines with weaker graphics cards exhibit these types of problems. So based on that our educated guess is that the problem is with WPF Rendering (VS2010 UI was rebuilt in WPF) on these weaker machines is what gets stuck. Never saw a problem running VS2010 on Windows 7. Time to upgrade the OS ... --- Adar Wesley
Seems to make sense, though I used it under XP for a good while without problems as well. It was on the same hardware, though. Generally I'm just happy with VS2008. It's really a first-class piece of software. I also use it in my own business that I'm starting and I see no reason to retool any time soon. I purchased VS2008 "Standard" a year or two ago and added Active Reports 6 to it a couple months ago which pretty much brings it up to "Pro" level. With it, SQL 2008 Express and VSS it's a nice set up. Very few, if any, problems - certainly nothing I can't work around. Cheers, -Max