Updating DscResources.psd1 for new version leaves old version of M365DSC.CompositeResources

[martincaddick]

Updating the DscResources.psd1 from 1.24.1211.1 to 1.25.122.1 works mostly.

Correctly uninstalls the old version of Microsoft365DSC and installs the new version.

However, it leaves the old version of M365DSC.CompositeResources.

ModuleType Version       Name                       ExportedCommands
---------- -------       ----                       ----------------
Script     1.25.122.100  M365DSC.CompositeResources New-M365DSCExampleDataFile
Script     1.24.1211.100 M365DSC.CompositeResources New-M365DSCExampleDataFile
Script     0.1.23        M365DSC.CRG                {New-CompositeResourceModule, Create-CompositeResource.build.M365DSC.CRG.ib.tasks}
Script     0.4.3         M365DSCTools               {Add-ModulesToBlobStorage, Convert-M365DSCExportToPowerShellDataFile, Copy-Object, Get-Environmen...

[Rikijooe]

I have the same problem. The pipeline takes the newest version, but fails if there is the also the old version in the module folder. You need to delete it manual, to solve the issue.

[ykuijs]

You must be used a self-hosted agent. When using Microsoft hosted agents or Managed DevOps Pools (highly recommended to check-out this possibility, offers best of both worlds), each session will get a fresh, clean agents so you never run into this issue.

Will investigate how we can resolve this issue.