Closed SDMol closed 2 months ago
Hi @SDMol , thanks for reaching out.
Here are some steps for you to perform:
%localappdata%\Microsoft\VisualStudio
privateregistry.bin
elsewhere, then delete this file.Extensions
subfolderExtensionMetadata.mpack
elsewhere, then delete this file.After this, the extension should be listed as installed, and the AWS Extension should no longer report "Some Toolkit components could not be initialized. Some functionality may not work during this IDE session."
Please let us know whether or not you're back in a functional state after this.
@SDMol it seems like this issue might have been fixed based on your comment in a separate issue. If yes, please let us know if we can close this issue.
Yes
Computer (please complete the following information):
Install log
Not listed in "Installed" or "Update" extensions. Listed in Browse with "INSTALL" button. Clicking INSTALL gives a notice that the extension will be installed upon close. After closing VS, the installer comes up, spins for a few seconds, then says the package is already installed.
Output in VS: Toolkit Version: 1.56.0.0 Visual Studio: VS Community 2022, Version: 17.11.1
Some Toolkit components could not be initialized. Some functionality may not work during this IDE session. If this issue persists, please see guidance on https://github.com/aws/aws-toolkit-visual-studio/issues/452