/ResetSkipPkgs (devenv.exe)
Clears all options to skip loading added to VSPackages by users wishing to avoid loading problem VSPackages, then starts Visual Studio.
Devenv /ResetSkipPkgs
Fixed my extensions issues
I had the theme color, productivity, and coderush extensions installed. I couldn't figured out which one was the offender, but using this switch helped reset my ide to keep from crashing.
- 8/18/2010
- huycool
Fixed: the problem with wpf visual designer
I had a problem with xaml designer, I was getting this error -
Devenv /ResetSkipPkgs solved the problem.
Please see this thread for details -
http://social.msdn.microsoft.com/forums/en-US/vswpfdesigner/thread/053dc5c3-27fe-4ea2-a7f5-5c6cf35000bb/
There is no editor available for "~~~/××.xaml" . Make sure the application for file type(.xaml) is installed.
Devenv /ResetSkipPkgs solved the problem.
Please see this thread for details -
http://social.msdn.microsoft.com/forums/en-US/vswpfdesigner/thread/053dc5c3-27fe-4ea2-a7f5-5c6cf35000bb/
- 12/18/2009
- akjoshi
Fixed: The Visual Studio language support for Style has not been installed.
I recently ran into this issue and once i executing this 'Devenv.exe /ResetSkipPkgs' resolve the issue.
- 8/4/2009
- Sonis
Project properties still not displaying
I have a similar problem. The project properties are not displayed for projects of type class libraries. For websites, the properties are displayed. I had a few addins like Dpack & slickedit installed. I uninstalled them & tried the command line switch, but that did not fix the problem.
Can anyone suggest what should i do?
- 5/15/2009
- justtesting
Fixed: The Visual Studio language support for Style has not been installed.
Once I ran VS with this switch, all my Intellisense came back.
- 12/29/2008
- hacker353
- 5/6/2009
- Thomas Lee
Fixed: Project Properties not Displaying
I had a problem where clicking on Project --> Properties would not bring up the properties for the project. No error message or anything...it just wouldn't display. I tried repairing VS, uninstalling/reinstalling VS, and reparing .Net 3.5 to no avail.
Running VS with this switch fixed the problem. Afterwards I was able to run VS normally and bring up Project Properties again.
- 5/1/2009
- Mike Tomlinson
- 5/6/2009
- Thomas Lee