One of our developers has come across an issue where when they install/upgrade dotnet-aspnetcoremodule-v2 to the latest stable version(16.0.22270), it removes v6.0.10 of the dotnet-6.0-aspnetruntime which had also been installed via Chocolatey
Up until now, we now haven't paid attention to the order in which we install packages assuming they were fairly idempotent. We installed the aspnetruntime before installed the aspnetcoremodule and for some reason when in that order, with the latest version of the aspnetcoremodule then the aspenetruntime gets removed!
I have tested having 6.0.10 of the runtime installed and then installing/upgrading aspnetcoremodule to 16.0.22232 (latest-1) and the issue didn't occur so I think it is something to do with the latest package.
I have managed to replicate this on several Windows 2016 server and several Windows 2019 servers (existing servers and freshly created) but I could not replicate on a desktop.
One of our developers has come across an issue where when they install/upgrade
dotnet-aspnetcoremodule-v2
to the latest stable version(16.0.22270), it removes v6.0.10 of thedotnet-6.0-aspnetruntime
which had also been installed via ChocolateyUp until now, we now haven't paid attention to the order in which we install packages assuming they were fairly idempotent. We installed the aspnetruntime before installed the aspnetcoremodule and for some reason when in that order, with the latest version of the aspnetcoremodule then the aspenetruntime gets removed!
I have tested having 6.0.10 of the runtime installed and then installing/upgrading aspnetcoremodule to 16.0.22232 (latest-1) and the issue didn't occur so I think it is something to do with the latest package.
I have managed to replicate this on several Windows 2016 server and several Windows 2019 servers (existing servers and freshly created) but I could not replicate on a desktop.
Steps to reproduce
Output