-
Notifications
You must be signed in to change notification settings - Fork 81
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
Remove double-slashes from Project Paths #165
Conversation
Not sure if we'll hit an msbuild issue again in the CI, as we originally had tried to do this when porting Behaviors back here: #20 (comment) |
Ugh, same issue as before in previous port of Behaviors project:
So, we've come around full circle, except this time the double-slashes cause more problems for the Behaviors project... Not sure if these threads have any info we can use: dotnet/msbuild#8985, dotnet/msbuild#2298, or dotnet/msbuild#4303 |
cc17699
to
85bc028
Compare
85bc028
to
652edec
Compare
Update tooling submodule to |
Helps with UWP project heads and old-project system now for some reason after single-experiment heads broke with #152 #164
There's still an issue with some projects (like Behaviors) that reference other projects within their source projects (like Animations).
The UWP single-component head isn't picking up that transitive dependency and failing to build. If you manually add the
Animations
reference to the UWP app head, then it starts working again... Assuming this is some issue with the old-style project, as the WASDK head works fine (before and after this change).We'll either have to follow-up with the tooling team and/or find a workaround for this in our props files...