We'd like the ability to specify to IVsPackageInstaller to install the 'newest' version of a package, when using a local pre-installed repository. Right now we have to specify an exact match of the semantic version, which introduces coupling between our code and our build scripts.
For our scenario (design-time-tooling) we're using a preinstalled package repository. This repo will typically include some 'new' version of packages that we own. In practice these differ by semantic version based on what release they correspond to:
AwesomePackage.4.0.0-alpha
AwesomePackage.4.0.0-beta
AwesomePackage.4.0.0-rtm
Packages coming from a beta branch would be 'AwesomePackage.4.0.0-beta' and from the active development branch might be 'AwesomePackage.4.0.0-rtm'. Our pre-installed repo would only contain one of these packages at a time -- so an MSI produced from beta branch would drop 'AwesomePackage.4.0.0-beta', etc.
We should be able to call IVsPackageInstaller::InstallPackage but not specify the version, so that we don't have to modify the package names in code when we integrate between branches.
Comments: Oh my bad. re-opened the bug.
For our scenario (design-time-tooling) we're using a preinstalled package repository. This repo will typically include some 'new' version of packages that we own. In practice these differ by semantic version based on what release they correspond to:
AwesomePackage.4.0.0-alpha
AwesomePackage.4.0.0-beta
AwesomePackage.4.0.0-rtm
Packages coming from a beta branch would be 'AwesomePackage.4.0.0-beta' and from the active development branch might be 'AwesomePackage.4.0.0-rtm'. Our pre-installed repo would only contain one of these packages at a time -- so an MSI produced from beta branch would drop 'AwesomePackage.4.0.0-beta', etc.
We should be able to call IVsPackageInstaller::InstallPackage but not specify the version, so that we don't have to modify the package names in code when we integrate between branches.
Comments: Oh my bad. re-opened the bug.