views:

865

answers:

7

I'm using VS2008 SP1 - don't know if this would have happened before I applied SP1 as I never tried it before yesterday. I attempted to debug a fairly simple XSLT file using VS2008 SP1 and got this crash from VS2008 SP1:


Microsoft Visual Studio

Unexpected error encountered. It is recommended that you restart the application as soon as possible.

Error: Unspecified error

File: vsee\pkgs\vssprovider\sccprj.cpp

A: 

looks like a visual source safe plugin problem.

Darren Kopp
A: 

I wouldn't be surprised at all. In my experience MS software is usually pretty good, but VS 2008 is just a really buggy app, I have only been using it everyday for about a month and a half and it has crashed on me 14 times (I started keeping track after 3) and I have submitted 2 bugs to be fixed, with another one I still need to submit. Its just terrible how unstable it still is.

corymathews
+1  A: 

We have reproduced this issue and will fix it in the next release of Visual Studio.

You are welcome to use Microsoft Connect site for reporting any issues related to Visual Studio.

Best regards,
Anton Lapounov
Data Programmability Team @ Microsoft

Antosha
A: 

I have this problem too. With or without SP1 but it doesn't crash VS and it still displays the resultant htm file once I okay the error.

I don't think it's related to visual source safe as I'm not using this. I do have the Team Explorer plug in so it might be something related to that.

Dan Revell
+3  A: 

Yes, sounds so. To use it, I had to disable VSS temporarily each time by setting Tools, Options, Source Control, Plug-in selection, Current source control plug-in to "None".

controlbreak
I use Team System but disabling that in the same way as described here solved the problem.
Si Keep
I've been having the same problem with VS2010 - any attempt to debug an XSLT led to a crash. Setting 'Current source control plugin' to 'none' in Options>Source Control also worked for me.
Daniel I-S
A: 

The same problem, after the stylesheet finishes processing, I get Unspecified error (and eveything seems ok after closing the error message box). Selecting source control plugin to "None" in VS options gets rid of the problem.

Jakub
A: 

Here's the link to Microsoft's bug and "fix" report, which includes info on the work around (disabling your source control plugin): VS2008 sp1 - XSLT Debugging Error in sccprj.cpp

schellack