Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Toolkit not showing as Installed in Visual Studio 2022. Amazon Q not working #483

Closed
rodrigoimparato opened this issue Dec 13, 2024 · 4 comments
Closed

Toolkit not showing as Installed in Visual Studio 2022. Amazon Q not working #483

rodrigoimparato opened this issue Dec 13, 2024 · 4 comments
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@rodrigoimparato
Copy link

On opening

  • Windows Version: Win32NT
  • OS version: 10.0.22621.0
    -Visual Studio Professional 2022 (17.12.3)
  • AWS Toolkit for Visual Studio Version: 1.61.0.0

The VS don´t show the Extension AWS Extension.

At last log show: INFO Amazon.AWSToolkit.VisualStudio.AWSToolkPackage - AWSToolkitPackage InitializeAsync completed successfully

However, the "AWS Extension" not showing in View.
@rodrigoimparato rodrigoimparato added the bug We can reproduce the issue and confirmed it is a bug. label Dec 13, 2024
@shruti0085
Copy link
Contributor

shruti0085 commented Dec 13, 2024 •
edited
Loading

Hi @rodrigoimparato , this sounds similar to #451
Can you check if you are seeing a similar message as this issue in the output window?
If yes, please try the steps listed in that issue and let us know if that helps.

If you continue to have issues please share your logs. You can jump to your logs for current VS session from the Extensions menu, selecting AWS Toolkit, and View Toolkit Logs.

@shruti0085 shruti0085 added the needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days label Dec 13, 2024
@rodrigoimparato
Copy link
Author

rodrigoimparato commented Dec 17, 2024 •
edited
Loading

I go to Extensions > AWS Toolkit > Getting Starded.
Sign in with specific credencials and successful!

@github-actions github-actions bot removed the needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days label Dec 17, 2024
@shruti0085
Copy link
Contributor

shruti0085 commented Dec 17, 2024 •
edited
Loading

Hi @rodrigoimparato, to confirm, did the above steps fix the issue for you?

@rodrigoimparato
Copy link
Author

Yes, it did.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rodrigoimparato @awschristou @shruti0085