Assembly conflicts #13
Comments
vaind
added a commit
that referenced
this issue
Feb 13, 2024
Some PowerShell versions turned out to be a problem to run, with dependency conflicts being the main reason. Since these are already out of support, it should be OK to stick to Powershell 7.2+ and Windows Powershell 5.1 See also #13 for followup to improve compatibility on the new PowerShell versions (7.2+)
vaind
added a commit
that referenced
this issue
Feb 13, 2024
Some PowerShell versions turned out to be a problem to run, with dependency conflicts being the main reason. Since these are already out of support, it should be OK to stick to Powershell 7.2+ and Windows Powershell 5.1 See also #13 for followup to improve compatibility on the new PowerShell versions (7.2+)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Loading multiple PowerShell modules that have dependency conflicts is a problem.
We may be able work around this for .net6+ (PowerShell 7.2+) by implementing AssemblyLoadContext.
.NET loads assemblies as needed so when a conflict arises, it may fail to load, throwing an exception.
related to: #12
The text was updated successfully, but these errors were encountered: