Azure / Azure/azure-powershell-migration

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

Open
#142 4 comments 0 reactions 1 assignee Claimed by @VeryEarly View on GitHub
enhancement VSCode Extension
Dominant language
PowerShell
Stars
36
Forks
27
PR merge metrics
No merged PRs in 30d

Description

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

![Image](https://github.com/user-attachments/assets/7d1ddbf3-be40-42e0-abb5-8845aa612380)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.