The Windows hosting package expects to be installed on a machine that has IIS installed, to the extent that there is a package parameter that does the following:
IgnoreMissingIIS - allow package installation even if IIS is not present (probably useless, as the native installer will not install anything)
This was not expected, as there is no guarantee that the database server will also have IIS installed.
Steps To Reproduce
Find a machine that doesn't have IIS installed
Install SQL Server
Install SQL Server Management Studio
Attempt to install the chocolatey-management-database package
Output Log
Workarounds
Manually install the dependent package, passing in a package parameter to ignore the fact that IIS is not installed:
choco upgrade chocolatey-management-database -y [OTHER OPTIONS]
# see https://docs.chocolatey.org/en-us/central-management/setup/database for OTHER OPTIONS
Or, alternatively, run the installation of the database package on a remote machine that has IIS installed. This assumes that there is a connection string available for a user that can alter the schemes of the database.
Proposed Solution
Change the dependencies on the chocolatey-management-database package to use a different package, that don't require IIS.
Switch to a version of Migrator that is built to contain the .NET Core Runtime
Description
The chocolatey-management-database package has a dependency on the dotnetcore-windowshosting package, which itself has a dependency to the aspnetcore-runtimepackagestore package.
The Windows hosting package expects to be installed on a machine that has IIS installed, to the extent that there is a package parameter that does the following:
This was not expected, as there is no guarantee that the database server will also have IIS installed.
Steps To Reproduce
Output Log
Workarounds
Manually install the dependent package, passing in a package parameter to ignore the fact that IIS is not installed:
Or, alternatively, run the installation of the database package on a remote machine that has IIS installed. This assumes that there is a connection string available for a user that can alter the schemes of the database.
Proposed Solution
Related Issues and Tickets
Zendesk Ticket, Zendesk Ticket
Done Checklist
┆Issue is synchronized with this Gitlab issue by Unito ┆Milestone: 0.6.2