dotnet / dotnet/project-system

FastUpToDateCheck does not work when CopyDocumentationFileToOutputDirectory is false

Open
#9,706 2 comments 0 reactions 0 assignees View on GitHub
Feature-Up-to-date Triage-Approved
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

## Visual Studio Version
17.14

## Summary
Set `true` and `false`

When building, the FastUpToDateCheck will always say `Output 'B:\mypath\ConsoleApp1\bin\Debug\net8.0\ConsoleApp1.xml' does not exist, not up-to-date. `

An explanation why this situation would occur. If you want to get rid of unused usings you need to enable documentation file generation for correct reporting but you might not want the DocumentationFile in the output.
See: https://github.com/dotnet/roslyn/issues/41640

## Expected Behavior
FastUpToDateCheck should know that no documentation file will be in the output and still consider the project up to date when it is missing

## Actual Behavior
FastUpToDateCheck always thinks the project is out of date

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.