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

Can't update the extension from 0.1.38 to 0.1.41 #6

Closed
MagicAndre1981 opened this issue Dec 29, 2024 · 18 comments
Closed

Can't update the extension from 0.1.38 to 0.1.41 #6

MagicAndre1981 opened this issue Dec 29, 2024 · 18 comments

Comments

@MagicAndre1981
Copy link

I can't update the extension from 0.1.38 to 0.1.41. Clicking on the VSIX opens Visual Studio Installer telling me everything is up to date

image

Clicking on Start opens VS 2022 again which offers me an update of your extension.

image

I use VS 2022 (x64) 17.12.3 on Windows 11 23H2.
@ThomasArdal
Copy link
Member

That's strange. What happens if you click that Update button inside of Visual Studio instead of upgrading through the vsix?

@MagicAndre1981
Copy link
Author

here happens the same. That is why I tried downloading the VSIX and installing the VSIX on my own.

@ThomasArdal
Copy link
Member

Can you try this:

  • Launch Visual Studio Installer.
  • Click Modify on your Visual Studio version.
  • Go to the Individual components tab.
  • Search for 'exception'.
  • Uncheck the 'Exception Visualizer' (might have a different name if you have an older version).
  • Click 'Modify'
  • Then install the extension from scratch.

image

@MagicAndre1981
Copy link
Author

here is what I see in the log:

29.12.2024 08:16:04 - Für die Erweiterung wird ein Upgrade von Version 0.1.38.0 durchgeführt.
29.12.2024 08:16:04 - Installiertes Produkt gefunden - Globaler Pfad
29.12.2024 08:16:04 - Erweiterungsdetails...
29.12.2024 08:16:04 - Identifier : ExceptionVisualizerVsix.59bb613d-3a6f-4cc0-90ae-e31743f8efde
29.12.2024 08:16:04 - Name : Exception Visualizer
29.12.2024 08:16:04 - Author : elmahio
29.12.2024 08:16:04 - Version : 0.1.41.0
29.12.2024 08:16:04 - Description : Show a debugger visualizer for exceptions in Visual Studio.
29.12.2024 08:16:04 - Locale : en-US
29.12.2024 08:16:04 - MoreInfoURL :
29.12.2024 08:16:04 - InstalledByMSI : False
29.12.2024 08:16:04 - SupportedFrameworkVersionRange : [0.0,2147483647.2147483647]
29.12.2024 08:16:04 - SignatureState : Unsigned
29.12.2024 08:16:04 - Unterstützte Produkte :
29.12.2024 08:16:04 - Microsoft.VisualStudio.Community
29.12.2024 08:16:04 - Version : [17.12,18.0)
29.12.2024 08:16:04 - ProductArchitecture : amd64
29.12.2024 08:16:04 - Microsoft.VisualStudio.Community
29.12.2024 08:16:04 - Version : [17.12,18.0)
29.12.2024 08:16:04 - ProductArchitecture : arm64
29.12.2024 08:16:04 - Verweise :
29.12.2024 08:16:04 - Voraussetzungen :
29.12.2024 08:16:04 - -------------------------------------------------------
29.12.2024 08:16:04 - Identifier : Microsoft.VisualStudio.Component.CoreEditor
29.12.2024 08:16:04 - Name : Visual Studio core editor
29.12.2024 08:16:04 - Version : [17.12,)
29.12.2024 08:16:04 - Signaturdetails...
29.12.2024 08:16:04 - Extension is not signed.
29.12.2024 08:16:04 - Microsoft.VisualStudio.ExtensionManager.RequiresInstallerException: Requested operation must be completed using Visual Studio Installer.

Multiple targets are currently not supported for this operation; retry with the instance you wish to target on the command line.
bei VSIXInstaller.ExtensionService.HandleExtensibilityType(Nullable1 extensionType, IList1 validSKUs, ProcessRestartInformation restartInfo, String extensionPackParentName)
bei VSIXInstaller.ExtensionService.GetInstallableDataImpl(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable1& skuData) bei VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable1& skuData)
bei VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
bei VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
bei VSIXInstaller.App.Initialize(Boolean isRepairSupported)
bei VSIXInstaller.App.Initialize()
bei System.Threading.Tasks.Task`1.InnerInvoke()
bei System.Threading.Tasks.Task.Execute()
29.12.2024 08:16:05 - Restarting into Visual Studio Installer at C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe with command line: "C:\Users\André\Downloads\ExceptionVisualizer.vsix"

@MagicAndre1981
Copy link
Author

Can you try this:

  • Launch Visual Studio Installer.
  • Click Modify on your Visual Studio version.
  • Go to the Individual components tab.
  • Search for 'exception'.
  • Uncheck the 'Exception Visualizer' (might have a different name if you have an older version).
  • Click 'Modify'
  • Then install the extension from scratch.

this works, but here it also opens the VS Setup UI during setup which I never seen before

image

@ThomasArdal
Copy link
Member

So, the new version is successfully installed now?

The screenshot you posted in the last comment. Isn't that the same window as the one from your first comment? With Updates selected in the first one and Installed selected in the last one.

@ThomasArdal
Copy link
Member

this works, but here it also opens the VS Setup UI during setup which I never seen before

Ah, you mean that the Visual Studio Installer is launched during installation of the extension now?

@MagicAndre1981
Copy link
Author

Ah, you mean that the Visual Studio Installer is launched during installation of the extension now?

yes, but I was not able to capture a screenshot of this where it showed "installing ExceptionVisualizer".

Any idea what this "Multiple targets are currently not supported for this operation; retry with the instance you wish to target on the command line" means?

@ThomasArdal
Copy link
Member

The newest versions of Visual Studio switch to using Visual Studio Installer to install extensions. It would seem that there is some kind of a problem with my extension if installed the "old" way.

As for the message in the log I don't know what that means but I will try to find out the cause of that.

@ThomasArdal
Copy link
Member

The error seems to be a general problem in Visual Studio. See:

https://developercommunity.visualstudio.com/t/Cant-Install-Any-Visual-Studio-Extensio/10458512
https://developercommunity.visualstudio.com/t/Unable-to-update-extensions-or-install-n/10446605
https://developercommunity.visualstudio.com/t/VSIX-installer-cannot-install-any-extens/10475376

I'll close this issue since I don't think there's much I can do to fix it ☺️

@MagicAndre1981
Copy link
Author

The newest versions of Visual Studio switch to using Visual Studio Installer to install extensions.

I tested several vsix updates and all install with VSIXInstaller.exe, only yours is installed via VS setup

image

Looks like this happens for new extensions that ue the new extension model from VisualStudio.Extensibility SDK

@ThomasArdal
Copy link
Member

Ah ok that makes sense. Thank you for providing that info 👍

@MagicAndre1981
Copy link
Author

Can you try this:

  • Search for 'exception'.
  • Uncheck the 'Exception Visualizer' (might have a different name if you have an older version).
  • Click 'Modify'
  • Then install the extension from scratch.

this is what I also had to do when trying to update to 0.1.45 . This is very annoying.

@ThomasArdal
Copy link
Member

ThomasArdal commented Jan 13, 2025 •
edited
Loading

@MagicAndre1981 I don't hope this is something that is needed on every update 🙈 Yeah, me too. I don't see any way to fix this currently. From the other links I provided it seems like this is a general problem with the new types of extensions :(

@MagicAndre1981
Copy link
Author

Can you please submit this to Microsoft as feedback? Maybe they gives this a higher priority if the extension developer itself reports it

@ThomasArdal
Copy link
Member

I tried creating one here: microsoft/VSExtensibility#450

@MagicAndre1981
Copy link
Author

thanks, I'll subscribe to the issue and look what Microsoft responds.

@MagicAndre1981
Copy link
Author

btw, can you please update the readme to list this update issue as a known issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ThomasArdal @MagicAndre1981