Resolving PowerShell Module Conflicts
Writing PowerShell modules sometimes means adding dependencies to an assembly file, such as an SDK. When the module you’re building has the same dependency as another module, a conflict occurs. What is the best way to handle the conflict, and how can you build your own assembly load context for your module?