@kzu commented on Mon, 19 Sep 2016 18:37:30 GMT@(ReferencePath) from regular assembly references contain metadata like ResolvedFrom={TargetFrameworkDirectory} or ResolvedFrom=ImplicitlyExpandDesignTimeFacades. It would be nice if the references added by ResolveNuGetPackageAssets annotated the reference as resolved by NuGet (maybe ResolvedFrom=Package?).
Currently, because this metadata isn't provided, they end up having ResolvedFrom={RawFileName}.
This would allow other tooling/targets to tell apart these references from others. (yes, I know the presence of the NuGetPackageId metadata can be used for the same, but for consistency with the way references are managed elsewhere, it would still be useful).
@kzu commented on Mon, 19 Sep 2016 18:37:30 GMT
@(ReferencePath)
from regular assembly references contain metadata likeResolvedFrom={TargetFrameworkDirectory}
orResolvedFrom=ImplicitlyExpandDesignTimeFacades
. It would be nice if the references added by ResolveNuGetPackageAssets annotated the reference as resolved by NuGet (maybeResolvedFrom=Package
?).Currently, because this metadata isn't provided, they end up having
ResolvedFrom={RawFileName}
.This would allow other tooling/targets to tell apart these references from others. (yes, I know the presence of the
NuGetPackageId
metadata can be used for the same, but for consistency with the way references are managed elsewhere, it would still be useful).