|
-
Dec 18th, 2012, 09:31 AM
#1
Thread Starter
PowerPoster
[RESOLVED] An exception has been encounterd. This may be caused by an extension.
Visual Studio 2012 Professional:
An exception has been encounterd. This may be caused by an extension.
I have included the log, cause I don't know where to look in the activity-log. Any chance someone can have a look and tell me what can be the problem? Thanks in advance.
ActivityLog.zip
-
Dec 18th, 2012, 09:52 AM
#2
Re: An exception has been encounterd. This may be caused by an extension.
Hello, have not looked at the activity log.
Can you tell us what line of code (and show code if possible) raised the exception?
-
Dec 18th, 2012, 06:08 PM
#3
Thread Starter
PowerPoster
Re: An exception has been encounterd. This may be caused by an extension.
I get this message when I start Visual Studio. No code used what-so-ever.
-
Dec 18th, 2012, 09:02 PM
#4
Addicted Member
Re: An exception has been encounterd. This may be caused by an extension.
You are getting errors in something called TestWindow.Core.dll
You could try to start visual studio in safe mode which will start without addins or extensions. Then you could possible work out which extension is crashing.
use:
devenv.exe /SafeMode
-
Dec 19th, 2012, 09:57 AM
#5
Re: An exception has been encounterd. This may be caused by an extension.
It does seem like extensions are the core problem. If using devenv.exe /SafeMode as suggested does allow VS to load them under VS options disable all extensions, restart w/o SafeMode. Does VS start? Enable extensions, restart, what happens? If still having issues one of the VS config xml files may be corrupt and if so would suggest posting a question at MSDN Visual Studio Setup and Installation forum.
-
Dec 20th, 2012, 11:46 AM
#6
Thread Starter
PowerPoster
Re: An exception has been encounterd. This may be caused by an extension.
Thanks. Will let you know
-
Dec 21st, 2012, 07:07 AM
#7
Thread Starter
PowerPoster
Re: An exception has been encounterd. This may be caused by an extension.
Hi,
Thanks for the tip. It seems that the NuGet Package Installer was the troublemaker. Uninstalled it and no issues any more. Thanks again.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|