You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are cases where multiple referenced packages contain the same assembly (e.g. NewtonsoftJson.dll). Current implementation of RT causes all packages that contain the assembly to be marked as used, if the compiler reports this assembly as used. The idea is to refactor RT to rely on the actual file paths reported by the compiler and not translate them to assembly names.
The text was updated successfully, but these errors were encountered:
stan-sz
added a commit
to stan-sz/ReferenceTrimmer
that referenced
this issue
Mar 4, 2024
multiple referenced packages contain the same assembly
This implies the packages themselves are badly formed, which is in itself a problem which should be fixed.
Also, how do they even get disambiguated in the first place? Is it deterministic?
stan-sz
changed the title
Refactor RT to rely on assembly file path, not AssemblyName, for accuract
Refactor RT to rely on assembly file path, not AssemblyName, for accuracy
Mar 5, 2024
* Rely on file paths not assembly names
Fixed#83
* Switch to paths
* Fix for reference assemblies
* Add tests
* Fix
* bump minor version
* Fix GAC test case
* Update shared structure
* Rename to AssemblyPath
* code cleanup
* Feedback
There are cases where multiple referenced packages contain the same assembly (e.g. NewtonsoftJson.dll). Current implementation of RT causes all packages that contain the assembly to be marked as used, if the compiler reports this assembly as used. The idea is to refactor RT to rely on the actual file paths reported by the compiler and not translate them to assembly names.
The text was updated successfully, but these errors were encountered: