You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The functionality provided by the BuildCheck module is increasing, hence as part of the #10316 we would like to stabilize the behaviour by running the tests (manual) and fixing bugs if appeared during the effort.
Goal
Validate that documentation of BuildCheck is aligned with actual implementation.
Validate that MSBuild with enabled BuildCheck runs successfully on Dotnet Repositories ( MSBuild including )
Part 1
Steps:
Prepare repro project and validate/confirm that the documentation and actual implementation (main branch) are aligned
In case of finding a bug: Check if it is not reported already if not then please report it :) with the label "Area: BuildCheck"
In case something is not clear in Documentation that is also an issue, please report it.
Categories/Scope/How to s
Inbox (built-in) analyzers that run during the build execution.
How to:
BC0101 - shared-output-path ( Person to contact: jankrivanek)
BC0102 - double-writes ( Person to contact: jankrivanek)
BC0103 - used-environment-variable ( Person to contact: YuliiaKovalova)
Scope: Reproduce the BuildCheck errors on different OS: windows, unix, mac.
Context
The functionality provided by the BuildCheck module is increasing, hence as part of the #10316 we would like to stabilize the behaviour by running the tests (manual) and fixing bugs if appeared during the effort.
Goal
Part 1
Steps:
Categories/Scope/How to s
Inbox (built-in) analyzers that run during the build execution.
Custom Analyzers
Configuration
Tracing
-v:d
and times should be at the end of logsReplay mode
Part 2
This part contains only of running the MSBuild on existing project with BuildCheck enabled.
Steps:
The text was updated successfully, but these errors were encountered: