while updating packages at solution level, it checks for all the projects in solution irrespective of the fact that not all the updating packages are applicable for all the projects and construct installing/ uninstalling actions for all the projects. This is wrong, it should always check for the projects where list of updating packages applies.
This is a regression post 3.5.0 release for VS 2017.
More details from one of the customer repro: Customer was trying to update his own 15 packages from a local feed.
Current code with VS2017 - shows total 86 installs across 18 projects for different combination of 28 packages (even installing packages out of those 15)
Where as it should have shown total 38 installs across 6 projects for different combination of 15 packages.
This particular scenario regressed update performance by ~10 mins (almost 100% regression from base time)
while updating packages at solution level, it checks for all the projects in solution irrespective of the fact that not all the updating packages are applicable for all the projects and construct installing/ uninstalling actions for all the projects. This is wrong, it should always check for the projects where list of updating packages applies.
This is a regression post 3.5.0 release for VS 2017.
More details from one of the customer repro: Customer was trying to update his own 15 packages from a local feed.
Current code with VS2017 - shows total 86 installs across 18 projects for different combination of 28 packages (even installing packages out of those 15)
Where as it should have shown total 38 installs across 6 projects for different combination of 15 packages.
This particular scenario regressed update performance by ~10 mins (almost 100% regression from base time)