Use ReferencePathWithRefAssemblies.Identity instead of ReferencePath.ReferenceAssembly #92
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use ReferencePathWithRefAssemblies.Identity instead of ReferencePath.ReferenceAssembly
Related to #88.
Today we're using
ReferencePath.ReferenceAssembly
, which in practice is usually the correct value, butReferencePathWithRefAssemblies
is what is actually passed to the compiler in the end.In most cases, the
FindReferenceAssembliesForReferences
target ends up populatingReferencePath.ReferenceAssembly
if needed, and then populatingReferencePathWithRefAssemblies
withReferencePath.ReferenceAssembly
:However, there also exists a
ShimReferencePathsWhenCommonTargetsDoesNotUnderstandReferenceAssemblies
target with a comment which adds some nuance.According to the comment, the generated XAML projects do not call
FindReferenceAssembliesForReferences
and thusReferencePath.ReferenceAssembly
won't be set. TheShimReferencePathsWhenCommonTargetsDoesNotUnderstandReferenceAssemblies
shims up theReferencePathWithRefAssemblies
item though, which is why we should be using that instead ofReferencePath.ReferenceAssembly