Skip to content
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

Jump to bottom

Update links to point to 'stable' versions of BuildCheck documents #9437

Merged
merged 1 commit into from
Aug 16, 2024
Merged

Update links to point to 'stable' versions of BuildCheck documents #9437

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 7 additions & 6 deletions release-notes/9.0/preview/preview6/sdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,10 @@

Here's a summary of what's new in the .NET SDK in this preview release:

- [NuGetAudit now raises warnings for vulnerabilities in transitive dependencies](#nugetaudit-now-raises-warnings-for-vulnerabilities-in-transitive-dependencies)
- Addition of [`dotnet nuget why`](#dotnet-nuget-why) to find out why a transitive package is being used in your project
- [MSBuild BuildChecks](#msbuild-buildchecks) to help users enforce rules and invariants during their builds
- [SDK updates in .NET 9 Preview 6](#sdk-updates-in-net-9-preview-6)
- [NuGetAudit now raises warnings for vulnerabilities in transitive dependencies](#nugetaudit-now-raises-warnings-for-vulnerabilities-in-transitive-dependencies)
- [`dotnet nuget why`](#dotnet-nuget-why)
- [MSBuild BuildChecks](#msbuild-buildchecks)

SDK updates in .NET 9 Preview 6:

Expand Down Expand Up @@ -52,12 +53,12 @@ MSBuild has introduced a new tool called BuildChecks to help users enforce rules
Like Roslyn Analyzers, the goal of this feature is to not only detect problems, but ensure that problems don't re-introduce themselves into the build once fixed.

In this release, we have added two BuildCheck rules
- [BC0101 - Shared Output Path](https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck/Codes.md#bc0101---shared-output-path)
- [BC0102 - Double Write detection](https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck/Codes.md#bc0102---double-writes)
- [BC0101 - Shared Output Path](https://github.com/dotnet/msbuild/blob/main/documentation/specs/BuildCheck/Codes.md#bc0101---shared-output-path)
- [BC0102 - Double Write detection](https://github.com/dotnet/msbuild/blob/main/documentation/specs/BuildCheck/Codes.md#bc0102---double-writes)

BuildCheck analysis can be used by adding the `/analyze` flag to any MSBuild-invoking call, both for `dotnet` and for `msbuild.exe`.
For example, `dotnet build myapp.sln /analyze` would build the `myapp` solution and run all configured BuildChecks.

When a BuildCheck detects a problem, you should see a diagnostic just like any other MSBuild diagnostic for the project that triggered the problem.

You can read more about the BuildCheck system in our [design documentation](https://github.com/dotnet/msbuild/blob/main/documentation/specs/proposed/BuildCheck.md).
You can read more about the BuildCheck system in our [design documentation](https://github.com/dotnet/msbuild/blob/main/documentation/specs/BuildCheck/BuildCheck.md).
Loading