Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Clarify that SdkAnalysisLevel impacts more than just this warning #3447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 23, 2025
Merged

Clarify that SdkAnalysisLevel impacts more than just this warning #3447

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3f97e7c
Clarify that SDKAnalysisLevel impacts more than just this warning
nkolev92 Jul 18, 2025
1b0bba6
cleanup
nkolev92 Jul 18, 2025
1d4c361
Update docs/reference/errors-and-warnings/NU1302.md
nkolev92 Jul 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/reference/errors-and-warnings/NU1302.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,4 +51,5 @@ Here's how it functions:
- For SDK Analysis Level value **below 9.0.100**, using HTTP sources triggers a warning ([NU1803](NU1803.md)).
- Starting with SDK Analysis Level **9.0.100 or higher**, HTTP sources result in an error (NU1302) unless `AllowInsecureConnections` is explicitly enabled.


> [!WARNING]
> Changing SdkAnalysisLevel has other side-effects. Refer to the [`SdkAnalysisLevel`](/dotnet/core/project-sdk/msbuild-props#sdkanalysislevel) for a summary of the full scope of .NET SDK features affected.