-
Notifications
You must be signed in to change notification settings - Fork 106
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
Rework Fast Up To Date checks to correctly capture cs:winmd relationship #880
Conversation
@@ -110,12 +110,13 @@ $(CsWinRTIncludeWinRTInterop) | |||
<WriteLinesToFile File="$(CsWinRTResponseFile)" Lines="$(CsWinRTParams)" Overwrite="true" WriteOnlyWhenDifferent="true" /> | |||
<Message Text="$(CsWinRTCommand)" Importance="$(CsWinRTMessageImportance)" /> | |||
<Exec Command="$(CsWinRTCommand)" /> | |||
<!--To support Visual Studio's FastUpToDate builds, we need to cpature the CsWinRT relationship of *.cs: *.winmd. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spelling: 'capture'
Looks like this breaks the build when WinRT.cs doesn't get created. Specifically the one in authoring is that they are all generated in a temp dir and then fed to a source geneator. For authoring scenarios, we don't need to do this as it would be handled by the source generator so I think can do a conditional check on it to exclude those scenarios. |
…ft/CsWinRT into scottj1s/fast_up_to_date
fixes #879
see related issue:
Visual Studio Fast Up To Date build not working - CopyComplete marker is touched when no files are copied · Issue #7326 · dotnet/project-system (github.com)