.NET Standard 2 Base NuGet Package shows error for no apparent reason
Visual Studio 2017 (15.9.2) on Windows using .NET Standard 2.0.3 project.
The Dependencies node shows an exclamation because the NuGet base node is showing Exclamation in VS but none of the NuGet packages are showing an exclamation!
Do you know how to sort this out? I have just created this project from scratch while converting from PCL.
N.B. The project compiles as expected, this is a cosmetic problem.
visual-studio-2017 nuget nuget-package .net-standard-2.0
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
asked Nov 20 at 13:14
Adam
1,41911839
|
show 2 more comments
Visual Studio 2017 (15.9.2) on Windows using .NET Standard 2.0.3 project.
The Dependencies node shows an exclamation because the NuGet base node is showing Exclamation in VS but none of the NuGet packages are showing an exclamation!
Do you know how to sort this out? I have just created this project from scratch while converting from PCL.
N.B. The project compiles as expected, this is a cosmetic problem.
visual-studio-2017 nuget nuget-package .net-standard-2.0
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
asked Nov 20 at 13:14
Adam
1,41911839
so what is the warning in the errors window? Does the output window show anything for nuget?
– Martin Ullrich
Nov 20 at 13:44
You are right, the warning message is there. Silly me, thank you
– Adam
Nov 20 at 14:44
@Adam, please share the warning message here.
– Leo Liu-MSFT
Nov 20 at 15:40
I have this after updating packages. simply closing/reopen project solves it.
– magicandre1981
Nov 20 at 16:41
@magicandre1981 whenever there is something that I can't explain, I close and open, so already done.
– Adam
Nov 20 at 23:38
|
show 2 more comments
Visual Studio 2017 (15.9.2) on Windows using .NET Standard 2.0.3 project.
The Dependencies node shows an exclamation because the NuGet base node is showing Exclamation in VS but none of the NuGet packages are showing an exclamation!
Do you know how to sort this out? I have just created this project from scratch while converting from PCL.
N.B. The project compiles as expected, this is a cosmetic problem.
visual-studio-2017 nuget nuget-package .net-standard-2.0
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
asked Nov 20 at 13:14
Adam
1,41911839
Visual Studio 2017 (15.9.2) on Windows using .NET Standard 2.0.3 project.
The Dependencies node shows an exclamation because the NuGet base node is showing Exclamation in VS but none of the NuGet packages are showing an exclamation!
Do you know how to sort this out? I have just created this project from scratch while converting from PCL.
N.B. The project compiles as expected, this is a cosmetic problem.
visual-studio-2017 nuget nuget-package .net-standard-2.0
visual-studio-2017 nuget nuget-package .net-standard-2.0
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
asked Nov 20 at 13:14
Adam
1,41911839
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
asked Nov 20 at 13:14
Adam
1,41911839
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
edited Nov 21 at 12:00
Wai Ha Lee
5,723123663
5,723123663
asked Nov 20 at 13:14
Adam
1,41911839
asked Nov 20 at 13:14
Adam
1,41911839
asked Nov 20 at 13:14
Adam
1,41911839
1,41911839
so what is the warning in the errors window? Does the output window show anything for nuget?
– Martin Ullrich
Nov 20 at 13:44
You are right, the warning message is there. Silly me, thank you
– Adam
Nov 20 at 14:44
@Adam, please share the warning message here.
– Leo Liu-MSFT
Nov 20 at 15:40
I have this after updating packages. simply closing/reopen project solves it.
– magicandre1981
Nov 20 at 16:41
@magicandre1981 whenever there is something that I can't explain, I close and open, so already done.
– Adam
Nov 20 at 23:38
|
show 2 more comments
so what is the warning in the errors window? Does the output window show anything for nuget?
– Martin Ullrich
Nov 20 at 13:44
You are right, the warning message is there. Silly me, thank you
– Adam
Nov 20 at 14:44
@Adam, please share the warning message here.
– Leo Liu-MSFT
Nov 20 at 15:40
I have this after updating packages. simply closing/reopen project solves it.
– magicandre1981
Nov 20 at 16:41
@magicandre1981 whenever there is something that I can't explain, I close and open, so already done.
– Adam
Nov 20 at 23:38
so what is the warning in the errors window? Does the output window show anything for nuget?
– Martin Ullrich
Nov 20 at 13:44
so what is the warning in the errors window? Does the output window show anything for nuget?
– Martin Ullrich
Nov 20 at 13:44
You are right, the warning message is there. Silly me, thank you
– Adam
Nov 20 at 14:44
You are right, the warning message is there. Silly me, thank you
– Adam
Nov 20 at 14:44
@Adam, please share the warning message here.
– Leo Liu-MSFT
Nov 20 at 15:40
@Adam, please share the warning message here.
– Leo Liu-MSFT
Nov 20 at 15:40
I have this after updating packages. simply closing/reopen project solves it.
– magicandre1981
Nov 20 at 16:41
I have this after updating packages. simply closing/reopen project solves it.
– magicandre1981
Nov 20 at 16:41
@magicandre1981 whenever there is something that I can't explain, I close and open, so already done.
– Adam
Nov 20 at 23:38
@magicandre1981 whenever there is something that I can't explain, I close and open, so already done.
– Adam
Nov 20 at 23:38
|
show 2 more comments
1 Answer
1
active
oldest
votes
While the reason for the exclamation was not showing in the solution panel. The error was in the "Output" window in Visual Studio.
In my specific case, one of the referenced NuGets was not compatible with .NET Standards 2, but the NuGet itself did not show any warning in the solution explorer, however, if you've expanded it you will see a warning.
answered Nov 21 at 11:46
Adam
1,41911839
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%2f53393835%2fnet-standard-2-base-nuget-package-shows-error-for-no-apparent-reason%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
While the reason for the exclamation was not showing in the solution panel. The error was in the "Output" window in Visual Studio.
In my specific case, one of the referenced NuGets was not compatible with .NET Standards 2, but the NuGet itself did not show any warning in the solution explorer, however, if you've expanded it you will see a warning.
answered Nov 21 at 11:46
Adam
1,41911839
add a comment |
While the reason for the exclamation was not showing in the solution panel. The error was in the "Output" window in Visual Studio.
In my specific case, one of the referenced NuGets was not compatible with .NET Standards 2, but the NuGet itself did not show any warning in the solution explorer, however, if you've expanded it you will see a warning.
answered Nov 21 at 11:46
Adam
1,41911839
add a comment |
While the reason for the exclamation was not showing in the solution panel. The error was in the "Output" window in Visual Studio.
In my specific case, one of the referenced NuGets was not compatible with .NET Standards 2, but the NuGet itself did not show any warning in the solution explorer, however, if you've expanded it you will see a warning.
answered Nov 21 at 11:46
Adam
1,41911839
While the reason for the exclamation was not showing in the solution panel. The error was in the "Output" window in Visual Studio.
In my specific case, one of the referenced NuGets was not compatible with .NET Standards 2, but the NuGet itself did not show any warning in the solution explorer, however, if you've expanded it you will see a warning.
answered Nov 21 at 11:46
Adam
1,41911839
answered Nov 21 at 11:46
Adam
1,41911839
answered Nov 21 at 11:46
Adam
1,41911839
answered Nov 21 at 11:46
Adam
1,41911839
1,41911839
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.
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%2f53393835%2fnet-standard-2-base-nuget-package-shows-error-for-no-apparent-reason%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
so what is the warning in the errors window? Does the output window show anything for nuget?
– Martin Ullrich
Nov 20 at 13:44
You are right, the warning message is there. Silly me, thank you
– Adam
Nov 20 at 14:44
@Adam, please share the warning message here.
– Leo Liu-MSFT
Nov 20 at 15:40
I have this after updating packages. simply closing/reopen project solves it.
– magicandre1981
Nov 20 at 16:41
@magicandre1981 whenever there is something that I can't explain, I close and open, so already done.
– Adam
Nov 20 at 23:38