I'm not sure what would cause it to crash in both VS 2005 and VS 2008.
There have been very few issues that would Visual Studio to crash.
One possibility is an issue that I blogged about a while back:
http://weblogs.asp.net/nunitaddin/archive/2006/06/07/Security-Apps-Break-.NET-2.0-Remoting.aspx
I think most security applications & firewalls have been updated since
then. It is possible however that you're using an older version and
experiencing this issue.
Can I check that when you say "crash", Visual Studio is exiting rather
than hanging?
It might be worth installing VS 2005 SP1 if you're not already using
it. This has fixed a hanging bug has occurred on a few people's
machines. I'd be surprised if it also fixed it for VS 2008, but you
never know.
Let me know how you get on.
Regards,
Jamie.
--
http://www.testdriven.net
http://weblogs.asp.net/nunitaddin
> Could it be a Vista related problem?
>
It could be. Someone else did have a problem with TestDriven.Net
hanging on a Vista machine. In the end they came back with the
following:
"I think I've found the source of my problem, and you'll be pleased to know
it's not your code.
I spent a good part of yesterday working with MS Support services to
troubleshoot my Vista machine. The darn thing was crashing quite often, and
they found that my Broadcom NIC drivers needed to be upgraded from 10.9 to
10.62.
Fast forward to this morning. I'm setting up a nice test environment for
you and *poof* everything is working now.
Since I think you do remoting through TCP, I'm betting the upgraded NIC
driver solved more than one problem."
> Also is there any logging I could enable to identify at what point it
> "hangs" VS?
>
Yes. Can you try running Sysinternals DebugView in the background
before VS hangs. Please send me a copy of the log. Hopefully this will
give us some clues. You can find DebugView here:
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
Regards,
Jamie.
Thanks for the log file. I can see there was a
AccessViolationException thrown when TestDriven.Net attempted to
access one of Visual Studio's code model functions. It is possible
that either Visual Studio is corrupted or there's a problem with
another package or add-in. Are you using any extensions that didn't
come with the default VS 2005 or 2008 install? If you are, could you
try uninstalling them and repeating the test.
One thing that surprises me is that you're experiencing the same issue
with VS 2005 and VS 2008. The two versions are pretty well isolated.
This points to the possibility that it's a lower level COM issue. Have
you noticed any other strange errors on your machine?
Regards,
Jamie.
--
http://www.testdriven.net
http://weblogs.asp.net/nunitaddin