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

Dependency Warnings #2

Open
JustinGrote opened this issue Nov 26, 2022 · 1 comment
Open

Dependency Warnings #2

JustinGrote opened this issue Nov 26, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@JustinGrote
Copy link
Owner

JustinGrote commented Nov 26, 2022

While PowerShell allows to you install multiple versions of a module side-by-side, if that module contains conflicting assemblies, we may want to warn that assembing binding redirect will occur and instruct the user the order in which to load their modules if they choose to use them simultaneously. This will be output as a warning. We only want to do this if the module is a binary module (how to detect) and two versions are found to have incompatible ranges (e.g. one requires maximum of 3.0 and another is unbounded and there is a 4.0 release out.

@JustinGrote JustinGrote added the enhancement New feature or request label Nov 26, 2022
@JustinGrote
Copy link
Owner Author

The only two ways to realistically do this are:

  1. Search the module folder for assemblies (low performance)
  2. Match on RequiredAssemblies (doesn't work if the user loads assemblies via .psm1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant