-
Notifications
You must be signed in to change notification settings - Fork 334
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.
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
Adding the WindowsAppSDK to a C# project breaks VS FastUpToDate and causes it to always build. #1525
Comments
@Scottj1s do we have a contact in the VS project system who can look into what's tripping FastUpToDate? |
`File.GetLastWriteTimeUtc` can throw several exceptions. One of them (`NotSupportedException`) was not covered in our catch clauses. This exception was observed in microsoft/WindowsAppSDK#1525, where an invalid path string was being provided. When this exception is caught, the file is considered unavailable, and we log the path in the up-to-date check output. This will unblock further diagnosis.
I took a look into this from the VS side and filed PR dotnet/project-system#7698 to help diagnose this kind of issue in future. With that change, the output would now include:
You can see there's a very long semicolon-delimited list of paths being treated as a single path. This hint was present, but less obvious, before:
We can see the incorrectly formed path is coming from an |
Ok I think the issue is here: This was broken in microsoft/CsWinRT#880. Having said that, it might be reasonable to specify multiple paths in this way. I'll have to think about this. Any fix we made in VS for that would only apply in 17.1, so customers in 16.x or 17.0 would be out of luck. |
@Scottj1s can you transfer this issue to the CsWinRT repo? |
Describe the bug
After adding the WindowsAppSDK package to a C# class library, the FastUpToDate checks in VS no longer consider the project to be up to date. This is particular problematic for larger solution as it breaks the inner loop by building everything every time.
Steps to reproduce the bug
Expected behavior
Screenshots
N/A
Version Info
NuGet package version:
Microsoft.WindowsAppSDK 1.0.0-preview1
Visual Studio version:
VS 2019
VS 2022 Preview
Additional context
WinUI3TestApp.zip
The text was updated successfully, but these errors were encountered: