Skip to content
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

Find ref asms after ResolveReferences (#2139) #2147

Conversation

rainersigwald
Copy link
Member

Cherry-pick #2139 to the vs15.3-preview2 branch. Will need escrow approval.

e3a3d69 added a new FindReferenceAssembliesForReferences target, which
ran just before ResolveReferences. Dogfooding this revealed targets in
the VS SDK (at least) that manipulate @(ReferencePath) and are hooked in
as AfterTargets of ResolveReferences. That was silently ignored,
corrupting the user's build.

Fixes dotnet#2134 by moving FindReferenceAssembliesForReferences later in the
process, so anyone hooking ResolveReferences will see the changes they
make in the compiler.

This is not a fully general solution to the problem that someone might
hook an arbitrary point and manipulate @(ReferencePath), but it unbreaks
an obvious hook point.
@AndyGerlicher
Copy link
Contributor

@dotnet-bot test this please

@rainersigwald rainersigwald merged commit e7e7903 into dotnet:vs15.3-preview2 May 31, 2017
@rainersigwald rainersigwald deleted the ref-asm-after-ResolveReferences-prev2 branch May 31, 2017 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants