Does this hang on anyone else in here? Seems like I need to kill the task 6 times a day on this thing. Waiting patiently for SP2. >![]()
-
-
The biggest problem was with the initial install taking ages, but I too have and am experiencing rather protracted hangs.
I resolved to re-install Vista and VS 2008 SP1 but am still having these hangs. Yesterday for instance, for the whole day it kept hanging. Kill all the processes, reboot and things work for a while and then bam! Back to square one.
I guess I'm pleased that other folks are experiencing this, but because of my belief in the VS team, I never ventured to believe that VS itself could be at fault.
Roll on SP2 -
? what ? I am not having to kill any tasks .... what do you mean exactly ? the devenv.exe task ? or some other bit of VS 2008 ?
-
Yeah, the devenv.exe task. Could even be something as moving a file in the solution or copying some Xaml and moving it. Doesn't get a Not Responding, and VS2008 repaints if you move a window on top and off of it; just the entire interface is completely unresponsive.figuerres said:? what ? I am not having to kill any tasks .... what do you mean exactly ? the devenv.exe task ? or some other bit of VS 2008 ?
-
My main issue it the amount of memory it uses, leading to constant OutOfMemory exceptions.Harlequin said:
Yeah, the devenv.exe task. Could even be something as moving a file in the solution or copying some Xaml and moving it. Doesn't get a Not Responding, and VS2008 repaints if you move a window on top and off of it; just the entire interface is completely unresponsive.figuerres said:*snip*
Although this does seem to help. -
I haven't had any problems with it, except for it occassionally failing to register an assembly for COM interop due to a permission issue when building. This also happened before SP1.
-
do yu have Vista?spivonious said:I haven't had any problems with it, except for it occassionally failing to register an assembly for COM interop due to a permission issue when building. This also happened before SP1.
This is usually fixed by running as an Admin. -
I have problems too. Especially with XAML files. I dont even use the designer. Most of the time VS is crashing when closing XAML files or when closing solutions.
-
Mine actually hangs if I click a Xaml file to edit, and I already that file open. Go to another open file tab, fine. Go back to the one I opened but was already open, doesn't repaint. Odd behaviour.Horst0815 said:I have problems too. Especially with XAML files. I dont even use the designer. Most of the time VS is crashing when closing XAML files or when closing solutions. -
No, it happens on XP. I'm a local administrator too, which makes it even more odd. It doesn't happen every time, and restarting VS always fixes it, so it must be some file locking issue.SaraJoRedux said:
do yu have Vista?spivonious said:*snip*
This is usually fixed by running as an Admin. -
After SP1 the web designer quit working on my system. It doesn't hang, the program it just never shows the controls visually. Also, it won't switch to the the other views split, html markup, so I have to close the window with the x on top and then reopen the window in html markup mode. I followed the directions on this site, Troubleshooting "Visual Studio 2008 Design view hangs" issues, but it didn't help. My recommendation don't do SP1!
Thanks,
Chris -
Well I'm totally against using the design view anyways. Messes up too much codechrfue said:After SP1 the web designer quit working on my system. It doesn't hang, the program it just never shows the controls visually. Also, it won't switch to the the other views split, html markup, so I have to close the window with the x on top and then reopen the window in html markup mode. I followed the directions on this site, Troubleshooting "Visual Studio 2008 Design view hangs" issues, but it didn't help. My recommendation don't do SP1!
Thanks,
Chris
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.