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?
Have you ever wanted to wrap your integration logic in a custom binding for Azure Functions for use in any language? Let’s take a look at how to post a message to Discord by writing and registering a binding extension, and using it from Azure Functions examples in C# and PowerShell.