I'm happy to move this to a feature-request, though I'm not 100% sure. Please advise. We've observed that when we mix 3rd-party module imports from ISV's, it's quite common that we hit assembly version collisions.
A very common example:
- Module1 depends on Newton.Json, Version 6.0
- Module2 depends on Newton.Json, Version 9.0
We can't use both these modules in the same session. If we import Module1, then Module2, the cmdlets from Module2 throw claiming assembly version conflicts with Newton.Json. Our current work around is to kill the powershell process and start over with the other module import.
Should powershell isolate module imports into their own AppDomains? I'm happy to implement a repo, if this is not already filed.
I'm happy to move this to a feature-request, though I'm not 100% sure. Please advise. We've observed that when we mix 3rd-party module imports from ISV's, it's quite common that we hit assembly version collisions.
A very common example:
We can't use both these modules in the same session. If we import Module1, then Module2, the cmdlets from Module2 throw claiming assembly version conflicts with Newton.Json. Our current work around is to kill the powershell process and start over with the other module import.
Should powershell isolate module imports into their own AppDomains? I'm happy to implement a repo, if this is not already filed.