We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
NA
In https://github.com/dotnet/project-system/blob/main/docs/up-to-date-check.md there is a link to https://github.com/dotnet/project-system/blob/main/docs/fast-up-to-date-legacy.md which is a 404.
An article on FUDC for legacy-projects
404
I had to dig up the process for managing FUDC on old non-SDK projects here: https://github.com/dotnet/project-system/blob/b536d25b38d1a7770fb983c65c89b826f5af7a83/docs/up-to-date-check.md
The text was updated successfully, but these errors were encountered:
drewnoakes
No branches or pull requests
Visual Studio Version
NA
Summary
In https://github.com/dotnet/project-system/blob/main/docs/up-to-date-check.md there is a link to https://github.com/dotnet/project-system/blob/main/docs/fast-up-to-date-legacy.md which is a 404.
Steps to Reproduce
Expected Behavior
An article on FUDC for legacy-projects
Actual Behavior
404
User Impact
I had to dig up the process for managing FUDC on old non-SDK projects here:
https://github.com/dotnet/project-system/blob/b536d25b38d1a7770fb983c65c89b826f5af7a83/docs/up-to-date-check.md
The text was updated successfully, but these errors were encountered: