Right now the module only supports installation and uninstallation of modules. We could add support for the Update-Module cmdlet to update existing installations of modules, thus retaining only a single installed module rather than side-by-side installations.
How should we implement this, and should we implement it? Perhaps through an 'UpdateExistingVersion' property on the moduleresource that updates any modules it finds rather than installs a newer version?
Right now the module only supports installation and uninstallation of modules. We could add support for the Update-Module cmdlet to update existing installations of modules, thus retaining only a single installed module rather than side-by-side installations.
How should we implement this, and should we implement it? Perhaps through an 'UpdateExistingVersion' property on the moduleresource that updates any modules it finds rather than installs a newer version?