Installation issues

[JSaaS]

Description

Trying to install biztalkmigrator on a fresh Windows Server. Installed Chocolatey as described, added the path to choco.exe in the environment variable PATH.

Running "choc install biztalkmigrator" gives an error that the package cannot be found:

PS C:\Users\joscadmin> choco install biztalkmigrator
Chocolatey v0.11.1
Installing the following packages:
biztalkmigrator
By installing, you accept licenses for the packages.
biztalkmigrator not installed. The package was not found with the source(s) listed.
Source(s): 'https://community.chocolatey.org/api/v2/'
NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify --pre,
the package may not be found

Running the command with "--pre" starts the install but it installs version 0.5.1-beta, not version 1.0.0? It also hangs in the last step where the package wants to install chocolatey?

biztalkmigrator v0.5.1-beta-2020102860429 (forced) - Possibly broken
biztalkmigrator package files install completed. Performing other installation steps.
The package biztalkmigrator wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation

Environment and tool versions

• AIM Tool Version (aim --version): 0.5.1
• Windows Version (systeminfo): Microsoft Windows Server 2019 Datacenter
• Shell: PowerShell
• Shell Version $PSVersionTable: 5.1.17763.2090

Repro steps

Please list out the steps needed to repro the issue, or delete if this is a feature request.

Expected result

choco install biztalkmigrator should run and install version 1.0.0

Current result

Please describe what you are seeing, or delete if this is a feature request.

[probertdaniel]

Hi JSaaS - as detailed on the ChangeLog, you need to install using the --version argument to get v1.0.0:
choco install biztalkmigrator --version 1.0.0.

Chocolatey haven't yet formally approved v1.0.0 which is why you still need to provide a version number.
Let me know if you have any other issues - thanks!