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

Assembly Conflict Handling #3

Open
dustinlacewell opened this issue May 7, 2019 · 0 comments
Open

Assembly Conflict Handling #3

dustinlacewell opened this issue May 7, 2019 · 0 comments
Labels
Core Disunity.Core good first issue Good for newcomers help wanted Extra attention is needed

Comments

@dustinlacewell
Copy link
Contributor

dustinlacewell commented May 7, 2019

We need to ensure that no mods claim to contain assemblies that have the same name. During mod enumeration and metadata loading, similar to when dependency resolution happens, is the best time for this to happen. If two mods have the same name, we should take appropriate action, by warning the user that ModA and ModB and ModF all claim to have preload or runtime assemblies by name Foo.dll or whatever, and that ModA's assembly will be used.

Or we can refuse to continue with the mod loading process.

@dustinlacewell dustinlacewell changed the title Restore Conflict Resolution Assembly Conflict Handling May 25, 2019
@dustinlacewell dustinlacewell added Core Disunity.Core good first issue Good for newcomers help wanted Extra attention is needed labels Aug 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Disunity.Core good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant