Visual Studio Exception has been thrown by the target of an invocation

Question

0.00/5 (No votes)

See more:

VS2010

VS2012

I can't open Visual Studio 2010 & Visual Studio 2012 in my new Windows 7 64 bit.
The error is Exception has been thrown by the target of an invocation when application start.
I already install Visual Studio Update 2010 & 2012.
Some command they say because of environment path more than 2048 characters by MSDN Topic.

Visual Studio program file path are under C:\Program File (x86).
Resetting the PATH environment to below 2048 characters will solve.
How can I reduce PATH environment for Visual Studio error "Exception has been thrown by the target of an invocation"?

Otherwise, Please share if you have any suggestion for this issue.
Thank you.

Posted 12-Aug-14 20:42pm

MinChanSike

Updated 12-Aug-14 20:46pm

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2014-08-12T21:55:00

Solution 1

This error can be cause by many different situations and it is impossible to diagnose from the information provided. I would suggest you try:

Contact Microsoft for assistance. Or
Re-install Visual Studio, one at a time, and see if the problem still occurs.

Posted 12-Aug-14 21:55pm

Richard MacCutchan