Visual Studio 2017: The SDK resolver type “DotNetMSBuildSdkResolver” failed to load
I've just upgraded Visual Studio Community 2017 to the latest version (15.9.2).
I tried creating a new ASP.NET Core Web Application project. Although the project files got created ok, the project won't load into the Visual Studio Solution Explorer - when I try to load the project, VS shows the following message:
The SDK resolver type "DotNetMSBuildSdkResolver" failed to load. The type initializer for 'Microsoft.DotNet.MSBuildSdkResolver.VSSettings' threw an exception.
I have .NET Core SDK 2.1.500 installed.
Any ideas why this is happening? Unfortunately this is preventing me from working with this project.
(By the way - creating a ASP.NET Web Application (.NET Framework) (i.e. NOT core) works fine.
asp.net-core visual-studio-2017
asked Nov 22 '18 at 16:50
Mat SMat S
161
add a comment |
I've just upgraded Visual Studio Community 2017 to the latest version (15.9.2).
I tried creating a new ASP.NET Core Web Application project. Although the project files got created ok, the project won't load into the Visual Studio Solution Explorer - when I try to load the project, VS shows the following message:
The SDK resolver type "DotNetMSBuildSdkResolver" failed to load. The type initializer for 'Microsoft.DotNet.MSBuildSdkResolver.VSSettings' threw an exception.
I have .NET Core SDK 2.1.500 installed.
Any ideas why this is happening? Unfortunately this is preventing me from working with this project.
(By the way - creating a ASP.NET Web Application (.NET Framework) (i.e. NOT core) works fine.
asp.net-core visual-studio-2017
asked Nov 22 '18 at 16:50
Mat SMat S
161
Same here. Can't open any existing asp.net core projects
– Alexander
Nov 23 '18 at 15:59
add a comment |
I've just upgraded Visual Studio Community 2017 to the latest version (15.9.2).
I tried creating a new ASP.NET Core Web Application project. Although the project files got created ok, the project won't load into the Visual Studio Solution Explorer - when I try to load the project, VS shows the following message:
The SDK resolver type "DotNetMSBuildSdkResolver" failed to load. The type initializer for 'Microsoft.DotNet.MSBuildSdkResolver.VSSettings' threw an exception.
I have .NET Core SDK 2.1.500 installed.
Any ideas why this is happening? Unfortunately this is preventing me from working with this project.
(By the way - creating a ASP.NET Web Application (.NET Framework) (i.e. NOT core) works fine.
asp.net-core visual-studio-2017
asked Nov 22 '18 at 16:50
Mat SMat S
161
I've just upgraded Visual Studio Community 2017 to the latest version (15.9.2).
I tried creating a new ASP.NET Core Web Application project. Although the project files got created ok, the project won't load into the Visual Studio Solution Explorer - when I try to load the project, VS shows the following message:
The SDK resolver type "DotNetMSBuildSdkResolver" failed to load. The type initializer for 'Microsoft.DotNet.MSBuildSdkResolver.VSSettings' threw an exception.
I have .NET Core SDK 2.1.500 installed.
Any ideas why this is happening? Unfortunately this is preventing me from working with this project.
(By the way - creating a ASP.NET Web Application (.NET Framework) (i.e. NOT core) works fine.
asp.net-core visual-studio-2017
asp.net-core visual-studio-2017
asked Nov 22 '18 at 16:50
Mat SMat S
161
asked Nov 22 '18 at 16:50
Mat SMat S
161
asked Nov 22 '18 at 16:50
Mat SMat S
161
asked Nov 22 '18 at 16:50
Mat SMat S
161
asked Nov 22 '18 at 16:50
Mat SMat S
161
161
Same here. Can't open any existing asp.net core projects
– Alexander
Nov 23 '18 at 15:59
add a comment |
Same here. Can't open any existing asp.net core projects
– Alexander
Nov 23 '18 at 15:59
Same here. Can't open any existing asp.net core projects
– Alexander
Nov 23 '18 at 15:59
Same here. Can't open any existing asp.net core projects
– Alexander
Nov 23 '18 at 15:59
add a comment |
3 Answers
3
active
oldest
votes
Had same error for the last few day.
I found a temporary workaround this problem - starting Visual Studio as Administrator
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
add a comment |
This looks to be an issue that's been introduced in the latest Visual Studio 2017 release. On my Windows Server 2008 system (where I was having the issue), I uninstalled 15.9.2 and installed the previous version 15.8.9 - that version worked fine. I.e. I can now load all my ASP.NET Core projects into the solution. (To be sure, I reinstalled 15.9.2 and confirmed that that that version definitely still did not work).
answered Nov 27 '18 at 8:54
Mat SMat S
161
add a comment |
I got the same issue today, my envs: win10, VS2017 15.9.4
Just use "Repair" of visual studio installer, and after that it works!
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
add a comment |
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%2f53435365%2fvisual-studio-2017-the-sdk-resolver-type-dotnetmsbuildsdkresolver-failed-to-l%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Had same error for the last few day.
I found a temporary workaround this problem - starting Visual Studio as Administrator
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
add a comment |
Had same error for the last few day.
I found a temporary workaround this problem - starting Visual Studio as Administrator
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
add a comment |
Had same error for the last few day.
I found a temporary workaround this problem - starting Visual Studio as Administrator
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
Had same error for the last few day.
I found a temporary workaround this problem - starting Visual Studio as Administrator
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
answered Nov 23 '18 at 16:11
AlexanderAlexander
7517
7517
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
add a comment |
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
That didn't work for me. However, I've installed VS2017 on a different machine now (Windows 10 instead of Windows Server 2008) and that is working fine.
– Mat S
Nov 26 '18 at 9:04
add a comment |
This looks to be an issue that's been introduced in the latest Visual Studio 2017 release. On my Windows Server 2008 system (where I was having the issue), I uninstalled 15.9.2 and installed the previous version 15.8.9 - that version worked fine. I.e. I can now load all my ASP.NET Core projects into the solution. (To be sure, I reinstalled 15.9.2 and confirmed that that that version definitely still did not work).
answered Nov 27 '18 at 8:54
Mat SMat S
161
add a comment |
This looks to be an issue that's been introduced in the latest Visual Studio 2017 release. On my Windows Server 2008 system (where I was having the issue), I uninstalled 15.9.2 and installed the previous version 15.8.9 - that version worked fine. I.e. I can now load all my ASP.NET Core projects into the solution. (To be sure, I reinstalled 15.9.2 and confirmed that that that version definitely still did not work).
answered Nov 27 '18 at 8:54
Mat SMat S
161
add a comment |
This looks to be an issue that's been introduced in the latest Visual Studio 2017 release. On my Windows Server 2008 system (where I was having the issue), I uninstalled 15.9.2 and installed the previous version 15.8.9 - that version worked fine. I.e. I can now load all my ASP.NET Core projects into the solution. (To be sure, I reinstalled 15.9.2 and confirmed that that that version definitely still did not work).
answered Nov 27 '18 at 8:54
Mat SMat S
161
This looks to be an issue that's been introduced in the latest Visual Studio 2017 release. On my Windows Server 2008 system (where I was having the issue), I uninstalled 15.9.2 and installed the previous version 15.8.9 - that version worked fine. I.e. I can now load all my ASP.NET Core projects into the solution. (To be sure, I reinstalled 15.9.2 and confirmed that that that version definitely still did not work).
answered Nov 27 '18 at 8:54
Mat SMat S
161
answered Nov 27 '18 at 8:54
Mat SMat S
161
answered Nov 27 '18 at 8:54
Mat SMat S
161
answered Nov 27 '18 at 8:54
Mat SMat S
161
161
add a comment |
add a comment |
I got the same issue today, my envs: win10, VS2017 15.9.4
Just use "Repair" of visual studio installer, and after that it works!
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
add a comment |
I got the same issue today, my envs: win10, VS2017 15.9.4
Just use "Repair" of visual studio installer, and after that it works!
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
add a comment |
I got the same issue today, my envs: win10, VS2017 15.9.4
Just use "Repair" of visual studio installer, and after that it works!
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
I got the same issue today, my envs: win10, VS2017 15.9.4
Just use "Repair" of visual studio installer, and after that it works!
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
answered Dec 24 '18 at 9:19
John_JJohn_J
482615
482615
add a comment |
add a comment |
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%2f53435365%2fvisual-studio-2017-the-sdk-resolver-type-dotnetmsbuildsdkresolver-failed-to-l%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
Same here. Can't open any existing asp.net core projects
– Alexander
Nov 23 '18 at 15:59