The ASPx Blog

Good to know,.

Thanks very much

I wonder why such a problem has passed the beta testing yours and Microsoft?

The IDE is not really usable.

That is good news.  Looking forward to the fix.

That is good news!

Thank you very much

Nice to read this info... (the fix for the issue).... but... bad to read that VS2008 has some issues like the mentioned. I'm waiting some months more to make the migration to VS2008.

Regards

Pingback from  » Daily Bits - January 19, 2008 (Early Edition) Alvin Ashcraft’s Daily Geek Bits: Daily links plus random ramblings about development, gadgets and raising rugrats.

Take a look at: forums.microsoft.com/.../showpost.aspx

We are all having the same issue when it comes to editing source of a webform,  Hope it gets fixed soon or we will be forced to revert back to vs 2005...

Thanks guys...

Its running like an absolute dog without the fix so fingers crossed M$ get it released soon!

I really need this fix

Good to hear a fix is coming.  Let's hope it's sooner than later....life is too short to deal with this sort of performance.

Please do all you can to expedite the solution from MS.  It clearly is an MS issue, but you most know that it makes you both (DX and MS) look bad.  As a customer, I cannot justify spending money an a product that doesnt work for me, regardless of who is at fault.  Thanks

Is it just me or is VS2008 a fat bloated pig? This thing takes longer to load than video games. 2MB of ram and it just churns and churns and churns, just to load small projects.

If it does require alot of loading, why doesn't MS put a dialog box up or some indication telling you what it is doing?

Hey MS, quit adding features and just optimize the code and give us better error handling and verbose notifications.

Hi,

Yeah...I have found that 2008 slows down more and more.  A quick re-start usually solves the issue.  Also, only keep one page with a grid view open at a time.  Be nice once the patch is out.

2008 Loads very fast on my vista machine...so I'd think it's just you Skippy (1.5GB of RAM AND running a web server / SQL server).

VS 2005 was bad as well.  2008 takes it to a new level of bad.

For whatever reason, installing the latest expressapp release helped.  Not sure why, but that was forum post, and it did help everything, even though I'm not using it in my app.

I also note that like VS2005, VS 2008 has memory leaking issues, the longer you run the slower things get until you reboot.

I am thinking that a dual quad core with 32 gb of ram and striped 15K SAS drives MIGHT make VS2008 useable.  Just need to sell a lot more work...

Funniest part is even though VS has a long history of malfunctioning, bugs and memory leaks... it still is an unavoidable tool, more helpful than restraining.

My thoughs on VS2008 is that it looks like 2005 on steroids. Some 2005 bugs seems to be gone by now, and apart from sluggish performance, I didn't notice any new major bug.

For that reason, I'm glad I migrated to 2008 already. I don't regret it a second.

Still, I understand and share the pain of many developpers here, and like them, I'm waiting for the next version of VS, asking myself "which bugs will be fixed by then?".

Ahhh, MS...

Skippy: '2MB of ram and it just churns and churns and churns'

Maybe you need to pimp it up to 4Mb :)

Any word on the patch as of yet ?

The hot fix is available... Yes !!!

weblogs.asp.net/.../vs-2008-web-development-hot-fix-roll-up-available.aspx

Nice....

but the fix doesnt fix anything unfortunatly....

Unfortunatly no... :(

After I reinstall Visual Studio 2008 and Hotfix, it also still insanely slow for me when ASPxGridView in my webform . I use DXperience 7.3.7 trial edition.

I used an aspxgridview today, and discovered that my markup editing became slow. Searched and found this article. After installing the fix, markup typing is not hindered by any intellisense delays. Great!

Alright, my performance never came back after the fix.... But then I was trolling and found this, not exactly sure why it works like it does but Visual Studio 2008 is instant on rendering saving, toggleing views and working on the markup.

IE7

Tools->Internet Options->Advanced->Security section-> uncheck "check for publisher's certificate revocation.........  Fast VS 2008 again.

Yes that was the post.  On my dev machine I have done it and it works great.  Lesser of two evils imo.  1 minute toggle times between saves and views is draining the life out of me.

Aaaaaarrrrgggg! Does anybody know of any way to tweak the vs2008 IDE. I have a huge project to complete and the larger it gets the slower the IDE gets. I have tried everything I can think of the speed it but nothing. I am dying here :(

P.S. The rollup was a faust.

Thanks Mehul for the reply. I have tried the SP1 Beta but to be honest I dont see any improvement in the actual performance of VS 2008. I installed VS 2005 again and compared the project in both versions. VS 2005  rocks compared to VS 2008 which confirms this has nothing to do with the third party controls. I have tried tweaking the IDE but as soon as i open the web form with the ASPxGridView I can go to lunch during the response times (largely over exaggerated of course but you get the picture).

Hope the final SP is completed soon.....

I'll second Ross's comments, to a degree. I tried installing VS.2008 SP1 Beta specifically to try to solve this issue, but it didn't seem to produce any improvement whatsoever.

However, that being said, VS.2008 seems to perform better in my situation than does VS.2005.

What frustrates me right now is that I'm unable to do anything practical to speed things up, and even though I've presented the problem to DX support, they don't have any practical suggestions either, other than tell me to reduce the size of the page (difficult to do with an ASPxPageControl).

Is there a way to press the issue with Microsoft more forcefully?

Just having great fun dealing with Visual Studio 2008 even with the hotfix. I've come to the conclusion that MS must have given up performance testing or go through a user acceptance process.

What a complete pile of crap. It's about time MS got replaced their entire development team with individuals who have even the slighest concept of product quality.

Here's an idea rather than working round the clock to address serious issues, why not fix the issues before you release a product? Could it be that MS are entirely drivn by sales deadlines even if it screws the end user?

It's about time someone gave Steve B a kicking.

You name it, MS bloat it, from Vista now to Visual Studio.

I've upgraded my workstation to a quad core with 8gb of RAM and VS is still a dog.

I'm in the same boat.  Tried ScottGu's hotfix... am planning on install the SP1 beta now.  Have a production-SLN with 3 projects (typical DAL, BAL, UI separation)... and vs2008 is driving me crazy.   I hope to hear something soon!

It appears that Microsoft finally fixed the problem.  I just now downloaded and installed Microsoft Visual Studio 2008 Service Pack 1 Beta and my slowness problems vanished without making any settings changes suggested above.  Saving large ascx and aspx files happens almost instantly and switching between Source and Design views in VS 2008 happens without delay.  Previously, I was experiencing agonizing delays that got longer and longer as the page size grew.  I'm now happy to report that the Service Pack 1 Beta has fixed the problem for me.

Darryl...Don't know what planet with futuristic lightspeed technology you're living on...

Installed the HotFix, nothing changed....watching the HTML Designer follow my keyboard strokes is more painful than watching paint dry!

Uninstalled the HotFix, Installed SP1 Beta instead...no dice...Now I'd just rather eat glass....

P4 2.8, 3GB Ram, Vista Ult

(Only reason I use Vista is for IIS7 compatability...else I'd be full time on XP).

We just installed the lastest release of SP1 for VS 2008 and this had a definite improvement in the performance of this feature.  We were concerned this would not help based on the posts we have seen but it did have a big improvement for us.  We are still testing with this, but this look like it is a good fix for this right now.