Author |
Topic |
|
Senzin
New Member
4 Posts |
Posted - May 28 2013 : 1:07:07 PM
|
SHORT VERSION: I don't know that Visual Assist X is the problem, but it seems like there should be a way to manually uninstall it in the case that VS won't start.
LONG VERSION: So everything was working fine. Then I did multiple Windows updates and an update of the NuGet package manager. When I started Visual Studio 2012, there was an error message... which I didn't read. After I told it to stop showing me the message, VS closed. Now it closes immediately after starting, without the start page appearing. I don't see the Visual Assist X toolbar, but I do see its drop down menu.
Something similar to this happened when I updated Visual Assist X a few months ago. I kept getting an error message at start up, but there was no crash. I fixed it by disabling Visual Assist X, restarting VS, then re-enabling it. This time, however, VS just crashes before I can do anything.
I've tried disabling all extensions through the registry, but during the brief moment before VS crashes, I can still see the Visual Assist X drop down menu.
I don't know that Visual Assist X is the problem, but it seems like there should be a way to manually uninstall it in the case that VS won't start. I would just like to try this before I go and uninstall VS completely. |
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 28 2013 : 1:30:41 PM
|
Sorry to hear of the trouble.
In VS2012, VA is installed to your local AppData directory. You can simply delete the directory to remove VA from VS2012. This faq item explains how to locate the install directory: http://docs.wholetomato.com?W282
|
Edited by - sean on May 28 2013 1:31:04 PM |
|
|
Senzin
New Member
4 Posts |
Posted - May 28 2013 : 5:02:21 PM
|
Manually deleting Visual Assist X did stop the crashing, however, the following problems then occurred. I think I'm probably going to repair or reinstall, but I just thought I'd post this here to be thorough.
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 28 2013 : 6:41:26 PM
|
Before reinstall, try creating a temporary user account and see if vs2012 will work with it. That will tell you if the problem is system-wide or if it is specific to your user configuration. If it works ok with your new temp account, then rather than reinstall VS2012, rename C:\\Users\\<username>\\AppData\\Local\\Microsoft\\VisualStudio\\11.0 to 11.0.bak. See if VS2012 then starts properly. |
|
|
Senzin
New Member
4 Posts |
Posted - May 28 2013 : 10:48:41 PM
|
Too late. I uninstalled and then reinstalled VS2012. Although, I wasn't terribly thorough with the uninstall. I didn't seek out and destroy installation folders, settings or registry entries.
After reinstalling, everything worked, but for some reason the "[...]\\Microsoft Visual Studio 11.0\\VC\\include" folder was empty except for two files. I didn't even have iostream. So I installed VS2012 update 2 and that fixed everything. I finally installed Visual Assist X again and now everything works fine.
Whew, that was a painful 6 hours. |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - May 28 2013 : 10:59:51 PM
|
Hope it stays healthy for you. |
|
|
|
Topic |
|