:sparkles: New cmdlet(s) for ModuleToRemove.txt to uninstall a package

[FH-Inway]

It would be nice to have cmdlets available that would make the process of uninstalling a package easier and automatable.

I propose two new cmdlets:

• New-D365ModuleToRemove: This would take a list of module names (would be nice if the output of Get-D365Module could be used as input as well) and generate a ModuleToRemove.txt file according to the Microsoft documentation.
• Add-D365ModuleToRemove: This would take the file path of a ModuleToRemove.txt or the output of New-D365ModuleToRemove as well as the file path of a deployable package and add the ModuleToRemove.txt to the deployable package in the package/AOSService/Scripts folder.

I'm also thinking about adding a parameter to Add-D365ModuleToRemove to provide module names so it can internally create the ModuleToRemove.txt file. This way the user would not have to work with two but just one cmdlet.

While researching this idea, I came upon How to add ModuleToRemove.txt to your package during MsDyn365FO build by @PaulHeisterkamp , which explores a similar idea and provides some PowerShell snippets to get started.

[Splaxi]

Awesome idea!

Let's make it happen 💪

[FH-Inway]

The existing cmdlet New-D365ISVLicense does basically the same thing as the proposed Add-D365ModuleToRemove cmdlet. I propose the logic gets refactored out into an internal function Add-FileToPackage, which could then be used by both cmdlets.

[FH-Inway]

Cmdlets New-D365ModuleToRemove and Add-D365ModuleToRemove are available as part of d365fo.tools starting with version 0.6.78.