-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
In SDK build, set BaseIntermediateOutputPath before it is used for MSBuildProjectExtensionsPath #802
Comments
Directory.Build.targets |
Directory.Build.props? |
😞 yes. |
Note, this issue will block the sdk repo from moving to |
Whoever fixes tests in VS will be my hero. Feel free to grab this. I think we can say it's an infrastructure only change and dogfooding aid and get permission to merge without ship room. |
@jonsequitur thought he could pursue this for us. Let's see if he can! |
This is done. |
…0190723.7 (dotnet#802) - Microsoft.AspNetCore.Mvc.Analyzers - 3.0.0-preview8.19373.7 - Microsoft.AspNetCore.Mvc.Api.Analyzers - 3.0.0-preview8.19373.7 - Microsoft.AspNetCore.Analyzers - 3.0.0-preview8.19373.7 - Microsoft.AspNetCore.Components.Analyzers - 3.0.0-preview8.19373.7
We're overriding BaseIntermediateOutputPath in our Common.props file, but this is after it's used to calculate the MSBuildProjectExtensionsPath, which means we aren't getting any of the NuGet generated props or targets files (and hence the props or targets from packages) as part of our build.
To fix this, we can use Directory.Import.targets, which will get imported before the MSBuildProjectExtensionsPath is evaluated. We can put a Directory.Import.targets in the src/ and test/ folders which imports our Common.props, and then remove the explicit Common.props import from all of our projects.
The text was updated successfully, but these errors were encountered: