“Visual Studio 2012 has stopped working” when solu

2019-01-24 05:20发布

When I open Visual Studio everything is fine, but when I open any solution, it comes up with an error:

Visual Studio 2012 for Windows Desktop has stopped working.

I'm beginning to get really frustrated now, can anyone help? I don't want to lose all of my work.

I formatted my computer yesterday, reinstalled all my software and used Visual Studio all day, it was fine. When I shut down the computer, it updated to the newest versions of windows update, then completed the update this morning when I turned it on, now I can't open any of my solutions again.

15条回答
smile是对你的礼貌
2楼-- · 2019-01-24 05:46

First I tried Reset All Settings: Tools -> Import / Export Settings -> Reset All Settings. I did not resolved the issue.

Deleting the entire deleted the entire folder, "%AppData%..\Local\Microsoft\VisualStudio\12.0" worked for me.

Thanks everyone for the help.

查看更多
女痞
3楼-- · 2019-01-24 05:46

Deleting the OBJ folder is what resolved this for me.

查看更多
男人必须洒脱
4楼-- · 2019-01-24 05:48

I had same problem and i also tried all above solutions but unable to fix it, even i re-install and repair Visual Studio. After 5-6 hours finally I got solution. Run Window + R and type below command. It will fix your problem. Thanks

"devenv.exe /ResetUserData"

查看更多
做个烂人
5楼-- · 2019-01-24 05:49

I came across this type of error last week working on VS2013, the solution for me is to start the Visual Studio installation and select 'Repair'.

查看更多
不美不萌又怎样
6楼-- · 2019-01-24 05:52

I had exactly the same problem, additionally I could not create new projects because of "no exports were found that match the constraint contract name" error. I made a small research and the answer from this question helped me to resolve both issues. Now I can create and open my previous projects. What I did is to delete this folder:

%AppData%\..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
查看更多
迷人小祖宗
7楼-- · 2019-01-24 05:55

Had this problem when trying to Debug an ASP.NET site.

Turns out my "Application Pool" (e.g. ASP.NET v4.0) had more than one "Maximum Worker Processes" and that was causing the problem.

查看更多
登录 后发表回答