Why VS2010 sucks today...
-
Trying to make a custom component in WinForms. Created the component and dragged it on to a Form for testing. Result: Practically every change I make to the component crashes VS2010 as soon as I open the Form designer... :mad: I understand some changes might mess up the designer (although I'd expect an error rather than a crash). I've done this before, but VS never crashed THIS much! :confused:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Trying to make a custom component in WinForms. Created the component and dragged it on to a Form for testing. Result: Practically every change I make to the component crashes VS2010 as soon as I open the Form designer... :mad: I understand some changes might mess up the designer (although I'd expect an error rather than a crash). I've done this before, but VS never crashed THIS much! :confused:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Trying to make a custom component in WinForms. Created the component and dragged it on to a Form for testing. Result: Practically every change I make to the component crashes VS2010 as soon as I open the Form designer... :mad: I understand some changes might mess up the designer (although I'd expect an error rather than a crash). I've done this before, but VS never crashed THIS much! :confused:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}I've also run into that (and other problems) and wish there was a way to temporarily turn off parsing till problem can be resolved.
This sig, like my mind intentionally left blank.
-
Have ya installed the VS 2010 SP1? The VS 2010 used to crash a lot in my system before installing the above update!
Not sure... Working from home on a virtual machine right now. On my own computer I never had these problems. I think VS crashed about 15 times in the last couple of hours... Even a simple modification like checking for a null value somewhere in my component crashes VS as soon as I get into the designer after the change. It's ridiculous. Not sure if I have the priviledges to install updates on this machine, but I'll ask my boss about it first thing in the morning tomorrow :thumbsup:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Not sure... Working from home on a virtual machine right now. On my own computer I never had these problems. I think VS crashed about 15 times in the last couple of hours... Even a simple modification like checking for a null value somewhere in my component crashes VS as soon as I get into the designer after the change. It's ridiculous. Not sure if I have the priviledges to install updates on this machine, but I'll ask my boss about it first thing in the morning tomorrow :thumbsup:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Also check class's ctor and onload functions... sometimes if you haven't checked for "DesignMode" property before executing some tasks like fetching values from db in above 2 methods, then they may fail and result in VS crashing without any proper error message, esp. so when you try to open the designer. :sigh:
-
Also check class's ctor and onload functions... sometimes if you haven't checked for "DesignMode" property before executing some tasks like fetching values from db in above 2 methods, then they may fail and result in VS crashing without any proper error message, esp. so when you try to open the designer. :sigh:
Nah, that's not it. I copied the constructor part from one of my other projects that never had that problem :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Not sure... Working from home on a virtual machine right now. On my own computer I never had these problems. I think VS crashed about 15 times in the last couple of hours... Even a simple modification like checking for a null value somewhere in my component crashes VS as soon as I get into the designer after the change. It's ridiculous. Not sure if I have the priviledges to install updates on this machine, but I'll ask my boss about it first thing in the morning tomorrow :thumbsup:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Naerling wrote:
Not sure... Working from home on a virtual machine right now.
That actually could be the problem... when you run a 'Debug' version of an application within the VS compiler... it is using physical cpu hardware registers DR0 through DR7. If the host machine has any applications using those registers there could potentially be a conflict. Best Wishes, -David Delaune
-
Not sure... Working from home on a virtual machine right now. On my own computer I never had these problems. I think VS crashed about 15 times in the last couple of hours... Even a simple modification like checking for a null value somewhere in my component crashes VS as soon as I get into the designer after the change. It's ridiculous. Not sure if I have the priviledges to install updates on this machine, but I'll ask my boss about it first thing in the morning tomorrow :thumbsup:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}I have the same issues on my work computer, it's a Windows XP PC :(. On my personal PC which is Windows 7 64b I barely have any crashes at all! It seems that on a 32bit Os VS can not see more than 2gb, and when as you start using add-ins you get frequent out of memory exceptions. I recently installed reSharper on my XP box and got out of mememory exception while loading a solution, I was not even able to work.
