[VS2022] The VsixPublisher.exe tool shipped with VS2022 seems to be broken

Installed product versions

Visual Studio: 2022 All Versions

Description

Invoking the VsixPublisher.exe tool shipped with Visual Studio 2022 inside the folder C:\Program Files\Microsoft Visual Studio\2022\Professional\VSSDK\VisualStudioIntegration\Tools\Bin ALWAYS throws an exception from the Command Line.

Steps to recreate

Go to above mentioned path of your flavour of Visual Studio (Community/Professional/Enterprise) Run this command from Command Line as a test of the VsixPublisher.exe tool: VsixPubliser.exe help

Current behavior

Unhandled Exception: System.MissingMethodException: Method not found: 'Void Microsoft.VisualStudio.RemoteControl.RemoteControlClient..ctor(Microsoft.VisualStudio.Utilities.Internal.IRegistryTools, System.String, System.String, System.String, Int32, Int32, Int32)'.
   at Microsoft.VisualStudio.Telemetry.TelemetryManifestManager.Start(String hostName, Boolean isDisposing)
   at Microsoft.VisualStudio.Telemetry.TelemetrySession.Start(Boolean checkPendingAsimovEvents)
   at Microsoft.VisualStudio.Sdk.VsixPublisher.TelemetryLogger.CreateTelemetrySession()
   at Microsoft.VisualStudio.Sdk.VsixPublisher.TelemetryLogger.get_TelemetrySession()
   at Microsoft.VisualStudio.Sdk.VsixPublisher.Program.Main(String[] args)
Vsix Publishing Tools 17.0.5233
Copyright (C) Microsoft Corporation. All rights reserved.

  deleteExtension               Delete an extension from the marketplace.

  deletePublisher               Delete a publisher from the marketplace.

  help                          Show the usage text

  login                         Add a publisher to the known publishers list.

  logout                        Remove a publisher from the known publishers list.

  publish                       Publishes an extension.

  version                       Display the version of this program.

Expected behavior

The publisher tool should show help results, but without the MissingMethodException thrown from it. The same exception is thrown no matter the command you run (help/login/logout/publish etc.). It seems the tool does execute the command as expected successfully, but not without an exception thrown, leading to a -1 Exit Code being returned when calling the tool from a script. This is leading to failures of my release pipelines.

Note: I apologize if this isn’t the right place to report this issue, I can close it and report the bug in a more appropriate Microsoft forum if someone can let me know. Thanks!

[reduckted]

I have just encountered this same problem when trying to publish an extension using GitHub Actions (build log is here).

"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VSSDK\VisualStudioIntegration\Tools\Bin\VsixPublisher.exe" publish -personalAccessToken *** -payload visual-studio\source\GitWebLinks\bin\Release\GitWebLinks.vsix -publishManifest visual-studio\publish.json

Unhandled Exception: System.MissingMethodException: Method not found: 'Void Microsoft.VisualStudio.RemoteControl.RemoteControlClient..ctor(Microsoft.VisualStudio.Utilities.Internal.IRegistryTools, System.String, System.String, System.String, Int32, Int32, Int32)'.
   at Microsoft.VisualStudio.Telemetry.TelemetryManifestManager.Start(String hostName, Boolean isDisposing)
   at Microsoft.VisualStudio.Telemetry.TelemetrySession.Start(Boolean checkPendingAsimovEvents)
   at Microsoft.VisualStudio.Sdk.VsixPublisher.TelemetryLogger.CreateTelemetrySession()
   at Microsoft.VisualStudio.Sdk.VsixPublisher.TelemetryLogger.get_TelemetrySession()
   at Microsoft.VisualStudio.Sdk.VsixPublisher.Program.Main(String[] args)
VSSDK: information VsixPub0038 : Uploaded 'Git Web Links' to the marketplace.
Error: The process 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VSSDK\VisualStudioIntegration\Tools\Bin\VsixPublisher.exe' failed with exit code 3762504530

Despite the error, it did succeed in publishing to the marketplace.

@wade0016 I tried using the VSSDK BuildTools NuGet package like you suggested, and it worked without any errors. Thanks for the workaround. 😄

[wade0016]

Sorry that this problem is happening. We are investigating a fix for this problem; in the meantime, it doesn’t appear the same problem happens when using the VSSDK BuildTools NuGet package. Would it be possible to use that instead?