VS2008 stability [modified]

[DetroitJ]

With the work I have been doing, ASP.NET/C#, 2008 seems to be a bit better than 2005. My gripe is with the rendering engne in the ASPX designer. I have a Theme and a StyleSheetTheme assigned to most of my pages and I get a stupid message about "This page contains invalid blah blah blah". However clicking on the refresh button makes the error go away until the next time I load the page. Couldn't VS just handle that better? I am going to be getting rid of the themes in my apps in favor of pure CSS but what a bother in the meantime.

[Paul Sanders the other one]

Just cancel the build and restart it. At least, this works for me (in C++ projects). I find that the debugger hangs periodically (again in C++ projects), and in such a way to also hang Explorer. The only solution is to kill devenv.exe, which you have to do from the command line as Explorer is not available. Bye bye context, breakpoints, bookmarks, watched variables etc :( I would upgrade to VS 2008 but the Edit 'n Continue feature is broken - it works but does not report compiler errors. This is a show-stopper for me as I use Edit 'n Continue extensively.

Paul Sanders http://www.alpinesoft.co.uk

[Paul Sanders the other one]

damnhotfix surely

Paul Sanders http://www.alpinesoft.co.uk

[Tomz_KV]

The major improvement needed, in my opinion, is the inaccuracy of error messages. Whenever a small syntax error occurs in code during debugging, hundreds of errors show up. Fixing that one syntax error, all errors are gone.

TOMZ_KV

[dino t socrates]

It's definitely not just you. I'm finally learning ASP.NET after years of straight C# and Windows Forms programming, and VS 2008 crashes on me all the time - up to a few times a day sometimes. I have no idea how stable VS 2005 was when it came to ASP.NET, but I could probably count on one or two hands how many times VS has ever crashed on me before doing ASP. Terry

[ClockMeister]

Tomz_KV wrote:

The major improvement needed, in my opinion, is the inaccuracy of error messages. Whenever a small syntax error occurs in code during debugging, hundreds of errors show up. Fixing that one syntax error, all errors are gone.

Cascading error-messages at compile time has always been an issue, particularly with C/C++. The only really valid "fix" for that would be to have the compiler give up on the first problem it finds which might not necessarily be a bad thing, however the intent is to try to point out as many things at one time as possible. Many times (as you have seen) one error causes the next to happen, so on and so on. I doubt you'll see this go away. -CB :D

[Dan Neely]

Hot fixes are treated as beta quality updates by MS for a reason. :laugh:

Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall

[Jorgen Sigvardsson]

dan neely wrote:

Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.

:laugh: I just had to look up the etymology of the word, and found this: cf. Swed. njugg "close, careful,". I swear I've never heard the word before in my life, so I'm assuming the word is really really old. Now that I do know about the word, I think I will start using it. Just to mess with other peoples' heads. :)

-- Kein Mitleid Für Die Mehrheit

[Dan Neely]

At a guess it came to the US in the late 19th/early 20th century. IIRC that's when we got a ton of Scandinavian immigrants.

Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall

[grgran]

I almost never see VS2008 crash, but then I almost never do ASP work. I understand that SP1 will be out by the end of summer ... hopefully it will fix your issues ... and address some of things like being able to sort properties (which I miss) ... wouldn't hurt to improve WPF/XAML intergration either (hope, hope)

[Jorgen Sigvardsson]

Yup. That's when times were really hard over here. If I'm not mistaken, pretty much all the states bordering to Canada, are infested with offspring of Scandinavian immigrants. Ja? ;) I remember visiting Seattle in -98, and damn, there were Norwegian stores everywhere! I even spoke Swedish with a store clerk (Swedes and Norwegians understand each other fairly easy).

-- Kein Mitleid Für Die Mehrheit

[TCHamilton]

I've had problems with both 2005 and 2008. 2005 when I bring on WCF/WPF extensions, and especially when using the MS C# Source Code Analyzer. I landed up abandoning the Code Analyser( FxCop seems to not be a problem, though). Vanilla versions were pretty stable on a clean install, but if there were beta's then things seem to get flaky / poof!/gone. Weird things happen with WF extensions and you really need Aaron Stebner's advice when things go bad.

Tom Hamilton Sacramento, CA

[JourneyWare]

Has the same problem. I was restarting VS2008 8-10 times per day. Did the following and have not had this issue since. 1.Run the command prompt under administrator a.Right click on command prompt and select run as administrator 2.Run this command: BCDEDIT /Set IncreaseUserVa 3072 (3072 is 3GB Virtual RAM) 3.Navigate to C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE a.Backup devenv.exe 4.Navigate to C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\ a.Verify that editbin.exe exists 5.If editbin.exe is there in the command prompt run this command: a."C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\editbin.exe" /LARGEADDRESSAWARE "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" b.You may get an error or two asking you to debug, just say no 6.Reboot your computer and hopefully it works for you

[Dan Neely]

I didn't realize there was a large presence out west, but I know Minnesota and northern Michigan had large populations. I find it kinda ironic that those people choose to settle in an area with a winter as harsh as the old country instead of taking the opportunity to move somewhere less bitter..

Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall

[MidwestLimey]

Oh, if only it were that easy :D When I say stuck, I mean kill the damn devenv.exe process stuck!

---

I'm largely language agnostic

---

After a while they all bug me :doh:

---

[Hardik Varma]

You probably have the display file names only checkbox checked

[Jorgen Sigvardsson]

I suppose it's all about what you're used to. A lot of immigrants were farmers, and I suppose they played it safe. All they had to do was to relocate - they didn't have to relearn everything that comes with a totally different climate. Personally, I would've immigrated to Florida or something like that. :)

[larryr ch2m]

It's not just you. I've had repeated crashes when trying to add icons to a menu strip in [Design] mode. The stupid program blows away everything I've done and usually I get obtuse (read meaningless) error messages and can no longer access the form I was just creating! :mad::mad::mad:

Expert (ex-spurt): ex = has-been; spurt = drip under pressure

[el delo]

I've been developing on Vista with VS05 since Vista shipped and for me VS05 was anything but stable on Vista. It used to crash so often that it went beyond frustrating to infuriating to so commonplace I hardly noticed. Sometimes not just several times in a day but several times per hour. It happened so often I wrote a command script to clean out the process space in the event there were orphaned processes etc, and put a shortcut on the desktop. Having VS05 crash, then clicking that link and restarting got to be so common I hardly noticed, it was just part of the dev process, like syncing/merging. We switched to VS08 several weeks back, and I've not had anywhere near the problems. To be honest I can't recall if it has crashed, because having VS/VSS (or one of the tools) crash on Vista has been so commonplace that, like I said, I hardly notice. Personally I long for the days of XP and stable VS05, when I could lock my machine at night in the middle of a debug session, come in the morning and unlock the machine and as soon as it repainted hit F10 and be in the next line of code, just where I left off (unless some type of timing etc was involved of course.) I can't even leave my Vista machine booted, much less logged-in/locked/in the middle of a debug session. Half the time Vista stops recognizing the KVM sometime over the course of the night and becomes completely unresponsive, at which point I have to power-down right in the middle of everything. That's much more painful than having to shut down everything and power down/up. I've tried contacting MS and/or submitting bugs, but all they do is immediately start questioning everything I do and so on, round and round, basically blowing me off and treating me like I'm the bug instead of their products.

[Trevortni]

I can't remember last time I had breakfast.