Aside from PSADT logging integration, this is precisely why my module exists. It even has a Repair-ADTWinGetPackageManager function to update WinGet, ensure Visual Studio Runtimes are installed, etc.
That looks pretty good to me. Its worth mentioning that you can’t really take some other module, slap PSAppDeployToolkit. on the front of it and all of a sudden its a PSADT extension. I doubt Evergreen will load like this because its psd1/psm1 files aren’t renamed also etc.
If you need to import non-PSADT modules into your PSADT environment, you should add the necessary Import-Module calls yourself.
This isn’t something we’ve thought about or considered, but if you’d love to chuck it up as a feature request on GitHub, we’ll be able to explore it as I can see the benefits for when you’re setting up an app packaging factory, etc. Sign in to GitHub · GitHub