Error Message: "Please install Az.Tools.Migration and make sure the version >= 1.1.5" on Extension Installation

[asilverman]

There are no instructions in the documentation for how to properly install Az.Tools.Migration and ensure the version is >= 1.1.5. Additionally, if this requirement is not met, every time I open VSCode, I get an annoying notification saying that the extension has an error.

Steps to Reproduce

1. Install the 'Azure PowerShell Tools' extension in VSCode.
2. Open VSCode.
3. Observe the error message in the output.

Expected Behavior

The extension should provide clear instructions on how to install Az.Tools.Migration and ensure the version is >= 1.1.5. Additionally, the extension should handle the absence of this module more gracefully, without showing an annoying notification every time VSCode is opened.

Actual Behavior

An error message is displayed, and there are no instructions on how to resolve it. The notification appears every time VSCode is opened, which is disruptive.

Environment

• Visual Studio Code version: 1.96.0-insider 64-bit
• Azure PowerShell Tools Extension version: 0.3.0
• Operating System: Windows 64-bit

Additional Context

Please provide detailed instructions in the documentation on how to install Az.Tools.Migration and ensure the version is >= 1.1.5. It would also be helpful if the extension could check for this requirement during installation and provide a one-time notification with instructions, rather than showing an error every time VSCode is opened.

Screenshots

[JayarajArockia]

This issue is caused by the Azure PowerShell Tools extension in VS Code. If you disable or uninstall this extension, the message to "Please install Az.Tools.Migration and make sure the version >= 1.1.5" will no longer appear.

[VeryEarly]

Hi @asilverman , please try below script to install version no lower than 1.1.5
Install-Module -Name Az.Tools.Migration -MinimumVersion 1.1.5

[asilverman]

I don't understand why doesn't the extension install all the necessary dependencies for it to function properly. Is there a technical limitation?