Hi together,
I have installed Visual Studio 2005 beta 2. I am using the VSS control embedded
into the Visual Studio. Since today when I try to make a VSS operation e.g. "check out"
or "undo checkout" a file from VSS the Studio crashes.
Even if I create a new project and make those VSS operations the studio crashes. When I use the standalone client from VSS everything is fine. I have reinstalled the beta 2 but the error
remains. I am lost!!
Please Help!
Cheers
Franz

Beta 2 Crash after VSS use
rwindsley
You can follow the instructions on this page that explains how to attach and obtain memory dumps: http://www.alinconstantin.com/webdocs/scc/UnspecifiedError.htm
Since in your case VisualStudio crashes, you should set Visual Studio to stop on AccessViolation errors. I suspect SourceSafe crashes with an AccessViolation, and the exception is not correctly handled by VisualStudio. Normally, VS should have caught crashes in the provider and disabled the source control provider; however there were some bugs in earlier VS2005 drops when VisualStudio crashed too after the provider crashed. If that's the case, we'd be interested in the first access violation, in the provider's code (ssscc.dll)
I hope this helps,
Alin
L M
please create a memory dump at the time of the crash and send it to me directly. it can be done easily by attaching another instance of Visual Studio process to the one that is about to crash, breaking and saving a minidump via Debug->Save as memory dump. be sure to select memory dump with Heap in the drop down box.
let me know if you have any questions.
-grigori
angus_grant
Best regards,
Franz
Prince_san
dump file and send it to you.
Cheers
Franz
PierreT
Re-insalling the OS doesn't solve the problem. I have tried to do it, but after installing VS 2005 and reloading my project, I have discovered that the error persists - IDE crashes when saving.
___________________________
Arnie
Dimitris Sv
I have sent you both the minidump file. It would be nice if you could send me
information about the error - and how I can fix it. I have seen another
posting in the newsgroup about this failure. The user told me, that only
a reinstall of the whole OS fixed this problem. I hope there is another way,
cause to reinstall the whole OS would be a disaster.
Best regards,
Franz