You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that 0.5.0 is out, I wanted to install 0.2.1 on a new system and then upgrade to 0.5.0 so that I would have both versions available to me. Typically to accomplish something like this I would simply Install-Module Microsoft.Graph -RequiredVersion 0.2.1, and then Update-Module Microsoft.Graph, however the Graph module bundle doesn't seem to handle this properly. Installing 0.2.1 at this point installs version 0.2.1 of Microsoft.Graph, along with 0.5.0 of all of the Microsoft.Graph.* modules in the bundle. That doesn't seem right. Shouldn't the Microsoft.Graph base module take dependencies on specific versions of the Microsoft.Graph* modules, so that they can be installed properly as a unit, and so that upgrading the base module results in upgrading any Microsoft.Graph* modules that are included in the bundle of the version you are upgrading to? Otherwise you're making it difficult for PowerShell script authors to work with a specific version unless they happen to be working with the latest version. AB#7447
The text was updated successfully, but these errors were encountered:
This is a legitimate concern. We are addressing it as part of a fix for #189. Microsoft.Graph will explicitly have its dependencies mapped to a specific version as suggested in #165 .
Uh oh!
There was an error while loading. Please reload this page.
Now that 0.5.0 is out, I wanted to install 0.2.1 on a new system and then upgrade to 0.5.0 so that I would have both versions available to me. Typically to accomplish something like this I would simply
Install-Module Microsoft.Graph -RequiredVersion 0.2.1
, and thenUpdate-Module Microsoft.Graph
, however the Graph module bundle doesn't seem to handle this properly. Installing 0.2.1 at this point installs version 0.2.1 ofMicrosoft.Graph
, along with 0.5.0 of all of theMicrosoft.Graph.*
modules in the bundle. That doesn't seem right. Shouldn't theMicrosoft.Graph
base module take dependencies on specific versions of theMicrosoft.Graph*
modules, so that they can be installed properly as a unit, and so that upgrading the base module results in upgrading anyMicrosoft.Graph*
modules that are included in the bundle of the version you are upgrading to? Otherwise you're making it difficult for PowerShell script authors to work with a specific version unless they happen to be working with the latest version.AB#7447
The text was updated successfully, but these errors were encountered: