Mixing
Visual Studio doesn't recognize .NET Framework 4 and up
The problem: Visual Studio Professional 2013 does not seem to recognize that .Net 4, or 4.5 through 4.7 are installed on my computer. It does not show ANY of these in the 'target framework' drop-downs. And my previous C# project that was made for 4.5 no longer loads or compiles (it used to work, on the same machine).
It looks like this: Target drop-down
I've wasted over five days on this problem. I searched the internet and this site numerous times already and read carefully every single page that even remotely has to do with this problem. I tried literally dozens of things, some of them several times in a different order, and NOTHING helps:
Re-installing .NET, all versions I could find 4.5- 4.7 (yes the SDK versions as well as multi-target versions).
Uninstalling all .NET installations, using the .NET cleanup tool, using the .NET repair tool, manually going over every .NET folder and registry key I could find and deleting those, and then reinstalling .NET 4.5 SDK.
Reinstalling and repairing Visual Studio 2013, or manually deleting all Visual Studio files and folders everywhere on the drive, and then re-installing it.
Installing various Windows SDKs separately, and installing MSBuild 2015.
When I install the same VS2013 install on another fresh VM machine, it works fine. I tried comparing both machines for days and even copying whole .Net/SDK/MSBuild folders and registry branches from the good VM to my machine, but could not find what was missing or misconfigured.
I tried debugging it using ProcessMonitor and other tools/logic carefully for 2 days but could find anything that helped (there are many thousands of lines that have to do with .NET so this is an impossible task.)
I tried using "SET TRACEDESIGNTIME=true" and looking at the logs. But I could not figure out which of the many settings are important or missing. I did notice that "SDK40ToolsPath" was empty and I fixed that by setting these values in the command line which were also mis-configured:
SET MSBuildExtensionsPath=C:Program Files (x86)MSBuild
SET MSBuildExtensionsPath32=C:Program Files (x86)MSBuild
And this seemed to do the trick for the path value, but still no .NET 4+ in VS. Perhaps there are other more basic properties I should be worrying about if SDK40ToolsPath wasn't set properly?
I am at my wits end and I hope that I do not have to reinstall Windows just for this because that would take another week. If anyone has any insight how VS detects .NET framework versions, or how to solve this problem, I would be most grateful.
.net visual-studio
asked Jan 1 at 18:08
ZevZev
1
|
show 2 more comments
The problem: Visual Studio Professional 2013 does not seem to recognize that .Net 4, or 4.5 through 4.7 are installed on my computer. It does not show ANY of these in the 'target framework' drop-downs. And my previous C# project that was made for 4.5 no longer loads or compiles (it used to work, on the same machine).
It looks like this: Target drop-down
I've wasted over five days on this problem. I searched the internet and this site numerous times already and read carefully every single page that even remotely has to do with this problem. I tried literally dozens of things, some of them several times in a different order, and NOTHING helps:
Re-installing .NET, all versions I could find 4.5- 4.7 (yes the SDK versions as well as multi-target versions).
Uninstalling all .NET installations, using the .NET cleanup tool, using the .NET repair tool, manually going over every .NET folder and registry key I could find and deleting those, and then reinstalling .NET 4.5 SDK.
Reinstalling and repairing Visual Studio 2013, or manually deleting all Visual Studio files and folders everywhere on the drive, and then re-installing it.
Installing various Windows SDKs separately, and installing MSBuild 2015.
When I install the same VS2013 install on another fresh VM machine, it works fine. I tried comparing both machines for days and even copying whole .Net/SDK/MSBuild folders and registry branches from the good VM to my machine, but could not find what was missing or misconfigured.
I tried debugging it using ProcessMonitor and other tools/logic carefully for 2 days but could find anything that helped (there are many thousands of lines that have to do with .NET so this is an impossible task.)
I tried using "SET TRACEDESIGNTIME=true" and looking at the logs. But I could not figure out which of the many settings are important or missing. I did notice that "SDK40ToolsPath" was empty and I fixed that by setting these values in the command line which were also mis-configured:
SET MSBuildExtensionsPath=C:Program Files (x86)MSBuild
SET MSBuildExtensionsPath32=C:Program Files (x86)MSBuild
And this seemed to do the trick for the path value, but still no .NET 4+ in VS. Perhaps there are other more basic properties I should be worrying about if SDK40ToolsPath wasn't set properly?
I am at my wits end and I hope that I do not have to reinstall Windows just for this because that would take another week. If anyone has any insight how VS detects .NET framework versions, or how to solve this problem, I would be most grateful.
.net visual-studio
asked Jan 1 at 18:08
ZevZev
1
Have you tried installing targeting packs?
– GSerg
Jan 1 at 18:40
Yes I wrote above multi-target packs, plus I reinstalled Visual Studio itself several times which includes those packs as part of its install.
– Zev
Jan 1 at 19:42
P.S. I forgot to mention I also installed Visual Studio Update 5 a couple of times
– Zev
Jan 1 at 19:43
Is there a reason you are still using 2013 and have not updated to a more recent edition? If you are using the free edition of 2013 there is a free edition of 2017 called the "Community" edition.
– Scott Chamberlain
Jan 1 at 20:14
Yes, because I need the Professional version and do not wish to purchase an upgrade at this time.
– Zev
Jan 1 at 20:18
|
show 2 more comments
The problem: Visual Studio Professional 2013 does not seem to recognize that .Net 4, or 4.5 through 4.7 are installed on my computer. It does not show ANY of these in the 'target framework' drop-downs. And my previous C# project that was made for 4.5 no longer loads or compiles (it used to work, on the same machine).
It looks like this: Target drop-down
I've wasted over five days on this problem. I searched the internet and this site numerous times already and read carefully every single page that even remotely has to do with this problem. I tried literally dozens of things, some of them several times in a different order, and NOTHING helps:
Re-installing .NET, all versions I could find 4.5- 4.7 (yes the SDK versions as well as multi-target versions).
Uninstalling all .NET installations, using the .NET cleanup tool, using the .NET repair tool, manually going over every .NET folder and registry key I could find and deleting those, and then reinstalling .NET 4.5 SDK.
Reinstalling and repairing Visual Studio 2013, or manually deleting all Visual Studio files and folders everywhere on the drive, and then re-installing it.
Installing various Windows SDKs separately, and installing MSBuild 2015.
When I install the same VS2013 install on another fresh VM machine, it works fine. I tried comparing both machines for days and even copying whole .Net/SDK/MSBuild folders and registry branches from the good VM to my machine, but could not find what was missing or misconfigured.
I tried debugging it using ProcessMonitor and other tools/logic carefully for 2 days but could find anything that helped (there are many thousands of lines that have to do with .NET so this is an impossible task.)
I tried using "SET TRACEDESIGNTIME=true" and looking at the logs. But I could not figure out which of the many settings are important or missing. I did notice that "SDK40ToolsPath" was empty and I fixed that by setting these values in the command line which were also mis-configured:
SET MSBuildExtensionsPath=C:Program Files (x86)MSBuild
SET MSBuildExtensionsPath32=C:Program Files (x86)MSBuild
And this seemed to do the trick for the path value, but still no .NET 4+ in VS. Perhaps there are other more basic properties I should be worrying about if SDK40ToolsPath wasn't set properly?
I am at my wits end and I hope that I do not have to reinstall Windows just for this because that would take another week. If anyone has any insight how VS detects .NET framework versions, or how to solve this problem, I would be most grateful.
.net visual-studio
asked Jan 1 at 18:08
ZevZev
1
The problem: Visual Studio Professional 2013 does not seem to recognize that .Net 4, or 4.5 through 4.7 are installed on my computer. It does not show ANY of these in the 'target framework' drop-downs. And my previous C# project that was made for 4.5 no longer loads or compiles (it used to work, on the same machine).
It looks like this: Target drop-down
I've wasted over five days on this problem. I searched the internet and this site numerous times already and read carefully every single page that even remotely has to do with this problem. I tried literally dozens of things, some of them several times in a different order, and NOTHING helps:
Re-installing .NET, all versions I could find 4.5- 4.7 (yes the SDK versions as well as multi-target versions).
Uninstalling all .NET installations, using the .NET cleanup tool, using the .NET repair tool, manually going over every .NET folder and registry key I could find and deleting those, and then reinstalling .NET 4.5 SDK.
Reinstalling and repairing Visual Studio 2013, or manually deleting all Visual Studio files and folders everywhere on the drive, and then re-installing it.
Installing various Windows SDKs separately, and installing MSBuild 2015.
When I install the same VS2013 install on another fresh VM machine, it works fine. I tried comparing both machines for days and even copying whole .Net/SDK/MSBuild folders and registry branches from the good VM to my machine, but could not find what was missing or misconfigured.
I tried debugging it using ProcessMonitor and other tools/logic carefully for 2 days but could find anything that helped (there are many thousands of lines that have to do with .NET so this is an impossible task.)
I tried using "SET TRACEDESIGNTIME=true" and looking at the logs. But I could not figure out which of the many settings are important or missing. I did notice that "SDK40ToolsPath" was empty and I fixed that by setting these values in the command line which were also mis-configured:
SET MSBuildExtensionsPath=C:Program Files (x86)MSBuild
SET MSBuildExtensionsPath32=C:Program Files (x86)MSBuild
And this seemed to do the trick for the path value, but still no .NET 4+ in VS. Perhaps there are other more basic properties I should be worrying about if SDK40ToolsPath wasn't set properly?
I am at my wits end and I hope that I do not have to reinstall Windows just for this because that would take another week. If anyone has any insight how VS detects .NET framework versions, or how to solve this problem, I would be most grateful.
.net visual-studio
.net visual-studio
asked Jan 1 at 18:08
ZevZev
1
asked Jan 1 at 18:08
ZevZev
1
asked Jan 1 at 18:08
ZevZev
1
asked Jan 1 at 18:08
ZevZev
1
asked Jan 1 at 18:08
ZevZev
1
1
Have you tried installing targeting packs?
– GSerg
Jan 1 at 18:40
Yes I wrote above multi-target packs, plus I reinstalled Visual Studio itself several times which includes those packs as part of its install.
– Zev
Jan 1 at 19:42
P.S. I forgot to mention I also installed Visual Studio Update 5 a couple of times
– Zev
Jan 1 at 19:43
Is there a reason you are still using 2013 and have not updated to a more recent edition? If you are using the free edition of 2013 there is a free edition of 2017 called the "Community" edition.
– Scott Chamberlain
Jan 1 at 20:14
Yes, because I need the Professional version and do not wish to purchase an upgrade at this time.
– Zev
Jan 1 at 20:18
|
show 2 more comments
Have you tried installing targeting packs?
– GSerg
Jan 1 at 18:40
Yes I wrote above multi-target packs, plus I reinstalled Visual Studio itself several times which includes those packs as part of its install.
– Zev
Jan 1 at 19:42
P.S. I forgot to mention I also installed Visual Studio Update 5 a couple of times
– Zev
Jan 1 at 19:43
Is there a reason you are still using 2013 and have not updated to a more recent edition? If you are using the free edition of 2013 there is a free edition of 2017 called the "Community" edition.
– Scott Chamberlain
Jan 1 at 20:14
Yes, because I need the Professional version and do not wish to purchase an upgrade at this time.
– Zev
Jan 1 at 20:18
Have you tried installing targeting packs?
– GSerg
Jan 1 at 18:40
Have you tried installing targeting packs?
– GSerg
Jan 1 at 18:40
Yes I wrote above multi-target packs, plus I reinstalled Visual Studio itself several times which includes those packs as part of its install.
– Zev
Jan 1 at 19:42
Yes I wrote above multi-target packs, plus I reinstalled Visual Studio itself several times which includes those packs as part of its install.
– Zev
Jan 1 at 19:42
P.S. I forgot to mention I also installed Visual Studio Update 5 a couple of times
– Zev
Jan 1 at 19:43
P.S. I forgot to mention I also installed Visual Studio Update 5 a couple of times
– Zev
Jan 1 at 19:43
Is there a reason you are still using 2013 and have not updated to a more recent edition? If you are using the free edition of 2013 there is a free edition of 2017 called the "Community" edition.
– Scott Chamberlain
Jan 1 at 20:14
Is there a reason you are still using 2013 and have not updated to a more recent edition? If you are using the free edition of 2013 there is a free edition of 2017 called the "Community" edition.
– Scott Chamberlain
Jan 1 at 20:14
Yes, because I need the Professional version and do not wish to purchase an upgrade at this time.
– Zev
Jan 1 at 20:18
Yes, because I need the Professional version and do not wish to purchase an upgrade at this time.
– Zev
Jan 1 at 20:18
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997762%2fvisual-studio-doesnt-recognize-net-framework-4-and-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997762%2fvisual-studio-doesnt-recognize-net-framework-4-and-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried installing targeting packs?
– GSerg
Jan 1 at 18:40
Yes I wrote above multi-target packs, plus I reinstalled Visual Studio itself several times which includes those packs as part of its install.
– Zev
Jan 1 at 19:42
P.S. I forgot to mention I also installed Visual Studio Update 5 a couple of times
– Zev
Jan 1 at 19:43
Is there a reason you are still using 2013 and have not updated to a more recent edition? If you are using the free edition of 2013 there is a free edition of 2017 called the "Community" edition.
– Scott Chamberlain
Jan 1 at 20:14
Yes, because I need the Professional version and do not wish to purchase an upgrade at this time.
– Zev
Jan 1 at 20:18