We do have a problem with our downloads that we provide. We have some powershell modules/cmdlets packed into an assembly, packed into a zip file. This file can be downloaded from our customers. The assembly is signed (like a normal exe/dll, I don't know if there's an other fancy cool new 'sign with appx manifest and who knows what else' way). ... but now, when our customers download those zip files and unpack them and try to import those modules, they get the information, that it cannot be loaded because of missing dependencies.
But the point is, that they have to right-click them, then unblock the files (downloaded from internet - bla bla) and after that they can use it.
My question now is... what can I do to prevent this? How do I have to distribute / pack those assemblies so that we don't run into this problem? It's quite annoying to deal with this over and over again...
Rudolf