The nuget operation failed due to one or more packages being incompatible with your project
I was trying to install the MathNet.Numerics package to my project (a class library), when I got this error:
The NuGet operation failed due to one or more packages being incompatible with your project. The '.NETPlatform,Version=v5.0' ('dotnet') project framework is deprecated. For more information about how to migrate your projects to a supported framework, please refer to themigration document (https://aka.ms/rugr4c). Would you like to continue with the project action(s) anyways?
This error also occured when I tried to update the Microsoft.NETCore.Portable.Compatibility package. Does anybody know what is causing this issue? I don't quite get what the error is saying even after some research, and I couldn't find anyone else with this issue. Thanks.
c# visual-studio visual-studio-2017 nuget
asked Nov 12 '18 at 3:37
JaxPayne
63
add a comment |
I was trying to install the MathNet.Numerics package to my project (a class library), when I got this error:
The NuGet operation failed due to one or more packages being incompatible with your project. The '.NETPlatform,Version=v5.0' ('dotnet') project framework is deprecated. For more information about how to migrate your projects to a supported framework, please refer to themigration document (https://aka.ms/rugr4c). Would you like to continue with the project action(s) anyways?
This error also occured when I tried to update the Microsoft.NETCore.Portable.Compatibility package. Does anybody know what is causing this issue? I don't quite get what the error is saying even after some research, and I couldn't find anyone else with this issue. Thanks.
c# visual-studio visual-studio-2017 nuget
asked Nov 12 '18 at 3:37
JaxPayne
63
add a comment |
I was trying to install the MathNet.Numerics package to my project (a class library), when I got this error:
The NuGet operation failed due to one or more packages being incompatible with your project. The '.NETPlatform,Version=v5.0' ('dotnet') project framework is deprecated. For more information about how to migrate your projects to a supported framework, please refer to themigration document (https://aka.ms/rugr4c). Would you like to continue with the project action(s) anyways?
This error also occured when I tried to update the Microsoft.NETCore.Portable.Compatibility package. Does anybody know what is causing this issue? I don't quite get what the error is saying even after some research, and I couldn't find anyone else with this issue. Thanks.
c# visual-studio visual-studio-2017 nuget
asked Nov 12 '18 at 3:37
JaxPayne
63
I was trying to install the MathNet.Numerics package to my project (a class library), when I got this error:
The NuGet operation failed due to one or more packages being incompatible with your project. The '.NETPlatform,Version=v5.0' ('dotnet') project framework is deprecated. For more information about how to migrate your projects to a supported framework, please refer to themigration document (https://aka.ms/rugr4c). Would you like to continue with the project action(s) anyways?
This error also occured when I tried to update the Microsoft.NETCore.Portable.Compatibility package. Does anybody know what is causing this issue? I don't quite get what the error is saying even after some research, and I couldn't find anyone else with this issue. Thanks.
c# visual-studio visual-studio-2017 nuget
c# visual-studio visual-studio-2017 nuget
asked Nov 12 '18 at 3:37
JaxPayne
63
asked Nov 12 '18 at 3:37
JaxPayne
63
asked Nov 12 '18 at 3:37
JaxPayne
63
asked Nov 12 '18 at 3:37
JaxPayne
63
asked Nov 12 '18 at 3:37
JaxPayne
63
63
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The nuget operation failed due to one or more packages being incompatible with your project
That because in the Visual Studio 2017 15.3:
You had two ways to target
.NET Standard: one was via letting a PCL
target .NET Standard. The other was via the new.NET Standard
project type. NuGet team disabled the UI for letting a PCL target
.NET Standardbecause it never worked well. It sounds like we’ve
accidentally broken something else that affects existing projects.
However, you can use the
.NET Standardproject type, i.e. File |
New Project | .NET Standard | Class Library (.NET Standard) to target .NET Standard 1.x/2.x, which can still be
consumed from .NET Core 1.x/2.x.
Check the blog Announcing .NET Standard 2.0 for some details
Hope this helps.
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
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%2f53255650%2fthe-nuget-operation-failed-due-to-one-or-more-packages-being-incompatible-with-y%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The nuget operation failed due to one or more packages being incompatible with your project
That because in the Visual Studio 2017 15.3:
You had two ways to target
.NET Standard: one was via letting a PCL
target .NET Standard. The other was via the new.NET Standard
project type. NuGet team disabled the UI for letting a PCL target
.NET Standardbecause it never worked well. It sounds like we’ve
accidentally broken something else that affects existing projects.
However, you can use the
.NET Standardproject type, i.e. File |
New Project | .NET Standard | Class Library (.NET Standard) to target .NET Standard 1.x/2.x, which can still be
consumed from .NET Core 1.x/2.x.
Check the blog Announcing .NET Standard 2.0 for some details
Hope this helps.
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
add a comment |
The nuget operation failed due to one or more packages being incompatible with your project
That because in the Visual Studio 2017 15.3:
You had two ways to target
.NET Standard: one was via letting a PCL
target .NET Standard. The other was via the new.NET Standard
project type. NuGet team disabled the UI for letting a PCL target
.NET Standardbecause it never worked well. It sounds like we’ve
accidentally broken something else that affects existing projects.
However, you can use the
.NET Standardproject type, i.e. File |
New Project | .NET Standard | Class Library (.NET Standard) to target .NET Standard 1.x/2.x, which can still be
consumed from .NET Core 1.x/2.x.
Check the blog Announcing .NET Standard 2.0 for some details
Hope this helps.
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
add a comment |
The nuget operation failed due to one or more packages being incompatible with your project
That because in the Visual Studio 2017 15.3:
You had two ways to target
.NET Standard: one was via letting a PCL
target .NET Standard. The other was via the new.NET Standard
project type. NuGet team disabled the UI for letting a PCL target
.NET Standardbecause it never worked well. It sounds like we’ve
accidentally broken something else that affects existing projects.
However, you can use the
.NET Standardproject type, i.e. File |
New Project | .NET Standard | Class Library (.NET Standard) to target .NET Standard 1.x/2.x, which can still be
consumed from .NET Core 1.x/2.x.
Check the blog Announcing .NET Standard 2.0 for some details
Hope this helps.
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
The nuget operation failed due to one or more packages being incompatible with your project
That because in the Visual Studio 2017 15.3:
You had two ways to target
.NET Standard: one was via letting a PCL
target .NET Standard. The other was via the new.NET Standard
project type. NuGet team disabled the UI for letting a PCL target
.NET Standardbecause it never worked well. It sounds like we’ve
accidentally broken something else that affects existing projects.
However, you can use the
.NET Standardproject type, i.e. File |
New Project | .NET Standard | Class Library (.NET Standard) to target .NET Standard 1.x/2.x, which can still be
consumed from .NET Core 1.x/2.x.
Check the blog Announcing .NET Standard 2.0 for some details
Hope this helps.
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
answered Nov 12 '18 at 7:40
Leo Liu-MSFT
17.8k21832
17.8k21832
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
add a comment |
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
Thank you so much!
– JaxPayne
Nov 12 '18 at 15:45
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
@JaxPayne, If above answer resolve your question, you could Accept it as an Answer. This can be beneficial to other community members reading this thread and we could close this thread, thanks.
– Leo Liu-MSFT
Nov 12 '18 at 16:01
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53255650%2fthe-nuget-operation-failed-due-to-one-or-more-packages-being-incompatible-with-y%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
