Within the Microsoft.VisualStudio.SDK package is the EnvDTE80 assembly. Inside it there are interfaces like CodeFunction2 that allow for an access modifier to be set (e.g. function.Access = vsCMAccess.Public). This used to work as expected for several years, but as I upgraded my extension CodeMaid to use v16.10.31321.278 of this package for VS2022 support it now has negative side effects to the code.

Here's an example:

namespace BugRepro
{
    public class Class1
    {
#if DEBUG
        [Obsolete]
#endif
        uint A(uint b) => b;
    }
}

If you attempt to set the access modifier on the method A it will delete the #endif line of code. Originally reported here: codecadwallader/codemaid#879

There have been several other issues reported too that we've traced back to attempting to set the access modifiers. It is affecting methods, properties, structs, etc. I can provide more examples if it would be helpful.

Thanks for looking into it and please let me know if there's any way I can be of help!

Hello, is there any documentation about creating a custom project property page on Visual Studio 2022?
My code for VS2019 doesn't work anymore, the pages don't appear nor the custom icon in the solution explorer...

A screenshot on how it used to be:

The CommandAttribute signature show ClientContext parameter is plural, but documentation shows singular. I'm assuming it should be plural, but not sure.

Also, could you provide an example of what the string should look like when it is multiple contexts?

Are there any plans to implement IntelliCode whole line completion public API?

There is a need in:

• an ability to determine that whole line completion is active/shown for the extension not to process Tab and Right Arrow keys and not to break the completion;
• an ability to pass a custom completion text to implement an integration of custom completion with IntelliCode whole line completion.

When building Dev17-targeted extensions using VS 16.10.1 I get the following error:

E:\nuget.cache\microsoft.vssdk.buildtools\17.0.2122-preview2\tools\VSSDK\Microsoft.VsSDK.targets(809,3): Error MSB4018: The "GetDeploymentPathFromVsixManifest" task failed unexpectedly.
System.TypeLoadException: Method 'get_JoinableTaskFactory' in type 'Microsoft.VisualStudio.Sdk.BuildTasks.ExtensionEngineHost' from assembly 'Microsoft.VisualStudio.Sdk.BuildTasks.17.0, Version=17.0.2122.24799, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.
   at Microsoft.VisualStudio.Sdk.BuildTasks.ExtensionManagerUtilities.GetExtensionEngine(ISettingsManager manager, Boolean deletePendingUninstalls)
   at Microsoft.VisualStudio.Sdk.BuildTasks.GetDeploymentPathFromVsixManifest.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()

Building extension targeting both Dev16 and Dev17 in Dev17 seems to work fine though.

This is required for our extension to build in the lab, which currently only has Dev16 installed.

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!

Microsoft.VisualStudio.TemplateWizardInterface has a reference to Microsoft.VisualStudio.Interop. However, Microsoft.VisualStudio.Interop has types that are duplicated in Microsoft.VisualStudio.Sdk which results in build errors when the tree of the references are used in a project.

Is seems that Microsoft.VisualStudio.TemplateWizardInterface is not designed to be used with Microsoft.VisualStudio.Sdk. Is that assumption correct? If so, is there any plans to include the logic for the template wizard extensions in the SDK meta package or we will need to reference the Microsoft.VisualStudio.Interop assembly from the Visual Studio installation folder in order to use the IWizard interface for example?

This crash now happens after exiting our custom events and before entering RegisterToVsEvents(). I cannot debug any further, is this due to changes to the event system, or something is checked in the background by VS?

The method RegisterToEventsAsync() is called in
protected override async Task InitializeAsync(CancellationToken cancellationToken, IProgress<ServiceProgressData> progress)

The examples show a TraceSource injected in Command implementations.
When I try to inject a TraceSource into a class implementing ExtensionPart the class isn't loading.

According to the docs this should be possible:
https://github.com/microsoft/VSExtensibility/blob/main/docs/new-extensibility-model/inside-the-sdk/extension-anatomy.md
The following services are provided by the SDK that can be used in constructor for any extension part:
...
TraceSource: A trace source instance is created on demand for each extension that can be used to record diagnostic information. These instances are registered with Visual Studio diagnostics provider which can be used to merge logs from multiple services and utilize future tooling to access real time logging. See Logging section for more information.

Is there more I need to do, then adding "TraceSource traceListener" as parameter in the ctor of an ExtensionPart? Is there a non-Command example around?

Kind regards, Florian.

Is this intended? Will it change?

It's quite important for us to have the right native libraries loaded for the xaml design process to work.

Suggestion for what to build out...

All the examples I've seen teach how to add NEW commands to VS Studio. I'm interesting in extending existing commands, and I've never been able to find docs on how to do this or even a listing of the existing commands.

For example: I want to extend/intercept the print command to programmatically invoke page setup first, fill in saved values for margins, and then run the print command as usual.

The VS 2022 Preview 5 release is available but the Microsoft.VisualStudio.SDK NuPkg is still at Preview 4.

https://www.nuget.org/packages/Microsoft.VisualStudio.SDK/

Do we know when this will be released? Want to update my extension for preview 5.

I have a custom project solution which does some cleanup tasks before the solutions are opened. With Visual Studio 2022, in the list of removed APIs, https://docs.microsoft.com/en-us/visualstudio/extensibility/migration/removed-api-list?view=vs-2022#asynchronous-solution-load-and-lightweight-solution-load one of the items are the interfaces IVsSolutionLoadManager and IVsSolutionLoadManagerSupport. After this removal, what is the recommended way to handle solution load.

Hello. Is there an event to hook on successful solution/project build? There was BuildEvents class in old VS Extensions.
I used
dte = (DTE2)await GetServiceAsync(typeof(DTE));
events = dte.Events;
buildEvents = events.BuildEvents;
buildEvents.OnBuildProjConfigDone += BuildEvents_OnBuildProjConfigDone;
buildEvents.OnBuildBegin += BuildEvents_OnBuildBegin;
buildEvents.OnBuildDone += BuildEvents_OnBuildDone;
referencesEvents = (ReferencesEvents)dte.Events.GetObject("CSharpReferencesEvents");
referencesEvents.ReferenceAdded += ReferencesEvents_ReferenceAdded;

Thank you

I've created two stubs for the AD7Engine, and PortSupplier.
I've also created a visix using the DebugLaunchProviderBase.

However, when hooking with the project I can step though the visix code and
public override async Task<IReadOnlyList> QueryDebugTargetsAsync(....)
which sets:
............................
............................
settings.LaunchDebugEngineGuid = Constants.DebugEngine170Guid;
settings.LaunchOptions = DebugLaunchOptions.StopDebuggingOnEnd;
settings.PortName = node;
settings.PortSupplierGuid = Constants.PortSupplier170Guid;

This works with visual studio 2019 all built with Any CPU. Finds both stubs and I can step though them to verify the hooks.
However, with visual studio 2022 I reach the end of public override async Task<IReadOnlyList> QueryDebugTargetsAsync(....), and then it complains it cannot find the file specified.

=====================================================================================

PkgDef contents:

[$RootKey$\AD7Metrics\Engine\{70A6FCFC-1A0A-4B61-A320-FD28F92D3732}]
"DumpWriting"=dword:00000001
"Attach"=dword:00000001
"CLSID"="{2A3220C9-8CA7-4F05-8747-520D6A78B61B}"
"DataBP"=dword:00000001
"Disassembly"=dword:00000001
"Name"="INtime"
"PortSupplier"="{E844B652-8854-478F-8237-206BCAFFDC4F}"
"SuspendThread"=dword:00000001
"SetNextStatement"=dword:00000001

[$RootKey$\CLSID\{2A3220C9-8CA7-4F05-8747-520D6A78B61B}]
"Assembly"="IntimeDbEngine"
"Class"="INtimeDebugger.Engine"
"InprocServer32"="$WinDir$\SYSTEM32\MSCOREE.DLL"
"CodeBase" ="$=HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\INTIME$VisualStudio\IntimeDbEngine.dll"

[$RootKey$\AD7Metrics\PortSupplier\{E844B652-8854-478F-8237-206BCAFFDC4F}]
"CLSID"="{C644EA21-DE61-4D47-A7E0-58B4BF26F1DA}"
"Name"="INtime Port Supplier"

[$RootKey$\CLSID\{C644EA21-DE61-4D47-A7E0-58B4BF26F1DA}]
"Assembly"="IntimeDbPorts"
"Class"="INtimeDebugger.PortSupplier"
"InprocServer32"="$WinDir$\SYSTEM32\MSCOREE.DLL"
"CodeBase" ="$=HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\INTIME$VisualStudio\IntimeDbPorts.dll"

I upgraded my project to reference the 17.0 preview 4 build tools and my VSIX no longer contains package references from nuget.
Preview 3 was fine. Preview 4 is broken.

Repro:

1. Create a new VSIX package project in VS 2022 preview
2. Manage the Nuget references and set the version of Microsoft.VSSDK.BuildTools to 17.0.3177-preview3
3. Also add a Nuget reference to Microsoft.ApplicationInsights 2.18.0
4. Build the VSIX
5. Rename the VSIX to .ZIP and examine the contents of the ZIP in Windows Explorer.
   

Notice the presence of Microsoft.ApplicationInsights.dll

5. Now upgrade the Microsoft.VSSDK.BuildTools reference to 17.0.4207-preview4
6. Rebuild the VSIX
7. Rename the VSIX to .ZIP and examine the contents:
   

Notice that the dependent assemblies (Microsoft.ApplicationInsights.dll, System.Buffers, System.Memory, etc.) are missing.

This breaks extension loading due to the missing files.

Migrating to Visual studio 2022 is presenting some challenges.
Our current implementation to our software is a 32 bit c++ dlls So I'll need to update the main wrapper to a 64bit version, but it uses other 32 bit components.
Question 1: Is the com object for IDebugEngine2 being supported, and for how long.?
Question 2: Do you recommend upgrading the c++ wrapper to a .Net version?

How do you create a casding menu to group multiple commands like Nuget Package Manager on the tools menu. We would prefer to group them like many other extensions group their commands.

After moving all the code to a Shared project, I was able to build from the same solution for VS2019 and VS2022.

My question is, can we also share resources such as images from the Shared project, not just code? Right now my assets/resources are duplicated.

We easily succeeded to have our extension compiling and working within VS2022 Preview, thanks for the great WIKI!

However when compiling our VSIX projects for VS2019, VS2017 and lower VS versions, we get plenty of conflict errors like.

Error	CS0433	The type 'Window2' exists in both 
'EnvDTE80, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' 
and 'Microsoft.VisualStudio.Interop, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'	
NDepend.VisualStudioExtension.Common3	
C:\My\NDepend\7.Current\NDepend.VisualStudioExtension.Common\Base\IVSVersionSwitch.cs	19	Active

Note that these VSIX projects were left untouched since we created a dedicated VSIX project for VS2022. Thus these untouched projects don't have any <PackageReference> item.

I've read the VSExtensibility FAQ advice:

• Add the following line to your CS Project to avoid duplicate assemblies: <PackageReference Include="<Name of offending assembly>" ExcludeAssets="compile" PrivateAssets="all" />

However adding these lines to NDepend.VisualStudioExtension.Common3.csproj doesn't help and the conflict errors persist.

<PackageReference Include="Microsoft.VisualStudio.Interop, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" ExcludeAssets="compile"  PrivateAssets="all"/>
<PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.0.0-previews-3-31605-261" ExcludeAssets="compile"  PrivateAssets="all"  />

At a point these conflict errors went away for no identified reasons and our VS2019 (and lower versions) packages compiled. However I noticed that all assemblies in the Microsoft.VisualStudio.SDK pkg were copied to the output directory. Thus I tried to add to the csproj things like this (based on this recommendation).

  <ItemDefinitionGroup>  
    <PackageReference ExcludeAssets="runtime;" />
  </ItemDefinitionGroup>

But not only it didn't help to avoid VS packages assemblies being copied, but the conflict errors came back now and I cannot find a way to get rid of those.

....and don't seem to be covered in any migration guide I've read.

Properties
ConfiguredProject
File
ItemName
ItemType

Methods
GetNamedCatalogsAsync()
TryGetCurrentCatalogSnapshot(out catalogSnapshot)
GetConfigurationGeneralPropertiesAsync();

to name a few. If migrating our extension to VS2022 what are these properties and methods now??

@JoeRobich and I have been working on updating Carnation to publish for VS 2022. It's a small package that is already compiling for AnyCPU and, luckily, was fairly easy to port.

During our port we've been having issues. We access the settings store on load and are hitting that Void Microsoft.VisualStudio.Shell.Settings.ShellSettingsManager..ctor(Microsoft.VisualStudio.Shell.Interop.IVsSettingsManager) does not exist.

You can get the current port from this branch: https://github.com/ryzngard/carnation/tree/vs2022-support

Are there known issues with getting the ShellSettingsManager? I didn't see anything in breaking changes and the latest packages seem to have this definition.

can i use winform or wpf in oop extensions?

Microsoft.VisualStudio.Setup.Configuration.Interop is listed in the SuppressFromVsix item group in Microsoft.VsSDK.targets. This prevents from including the assembly in the VSIX. Is this intentional? If so, is there an alternative API that we can use?

I was able to port the extension to VS 2022, and it works great.

The issue I am having is creating a single VSIX to target both 2019 and 2022. When installing the package on VS 2019, the errors below appear in the ActivityLog.xml.

Any help is greatly appreciated.

  <entry>
    <record>2127</record>
    <time>2021/07/16 18:23:44.588</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>Failed to set Public Key Token</description>
    <hr>80070057 - E_INVALIDARG</hr>
    <errorinfo></errorinfo>
  </entry>
  <entry>
    <record>2128</record>
    <time>2021/07/16 18:23:44.588</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.</description>
    <hr>80070057 - E_INVALIDARG</hr>
    <errorinfo></errorinfo>
    <path>Software\Microsoft\VisualStudio\16.0_5c531747Exp_Config\RuntimeConfiguration\dependentAssembly\codeBase\{7E3251B2-FB42-4E38-B22C-5FD281BD4413}</path>
  </entry>
.....
    <record>2913</record>
    <time>2021/07/16 19:44:37.953</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>CreateInstance failed for package Source: &apos;mscorlib&apos; Description: Could not load file or assembly &apos;Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos; or one of its dependencies. The system cannot find the file specified.&#x000D;&#x000A;System.IO.FileNotFoundException: Could not load file or assembly &apos;Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos; or one of its dependencies. The system cannot find the file specified.&#x000D;&#x000A;File name: &apos;Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos;&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)&#x000D;&#x000A;   at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)&#x000D;&#x000A;   at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)&#x000D;&#x000A;&#x000D;&#x000A;=== Pre-bind state information ===&#x000D;&#x000A;LOG: DisplayName = Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&#x000A; (Fully-specified)&#x000D;&#x000A;LOG: Appbase = file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/&#x000D;&#x000A;LOG: Initial PrivatePath = NULL&#x000D;&#x000A;Calling assembly : ClangPowerTools, Version=1.0.0.0, Culture=neutral, PublicKeyToken=818ea5269d1c16e6.&#x000D;&#x000A;===&#x000D;&#x000A;LOG: This bind starts in LoadFrom load context.&#x000D;&#x000A;WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().&#x000D;&#x000A;LOG: Using application configuration file: C:\Users\horat\AppData\Local\Microsoft\VisualStudio\16.0_5c531747Exp\devenv.exe.config&#x000D;&#x000A;LOG: Using host configuration file: &#x000D;&#x000A;LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.&#x000D;&#x000A;LOG: Post-policy reference: Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PublicAssemblies/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;WRN: Comparing the assembly name resulted in the mismatch: Major Version&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PublicAssemblies/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/TestWindow/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/TestWindow/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Platform/Debugger/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Platform/Debugger/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/x86/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/x86/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PublicAssemblies/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PublicAssemblies/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/TestWindow/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/TestWindow/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Platform/Debugger/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Platform/Debugger/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/x86/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/PrivateAssemblies/DataCollectors/x86/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///c:/users/horat/appdata/local/microsoft/visualstudio/16.0_5c531747exp/extensions/caphyon/clang power tools/7.4.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///c:/users/horat/appdata/local/microsoft/visualstudio/16.0_5c531747exp/extensions/caphyon/clang power tools/7.4.0/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.DLL.&#x000D;&#x000A;LOG: Attempting download of new URL file:///c:/users/horat/appdata/local/microsoft/visualstudio/16.0_5c531747exp/extensions/caphyon/clang power tools/7.4.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;LOG: Attempting download of new URL file:///c:/users/horat/appdata/local/microsoft/visualstudio/16.0_5c531747exp/extensions/caphyon/clang power tools/7.4.0/Microsoft.VisualStudio.Shell.15.0/Microsoft.VisualStudio.Shell.15.0.EXE.&#x000D;&#x000A;</description>
    <guid>{F564F9D3-01AE-493E-883B-18DEEBDB975E}</guid>
    <hr>80004005 - E_FAIL</hr>
    <errorinfo></errorinfo>

Seems like there are issues in 2022 trying to create your own Project System. For example, .myproj and custom setup.

Would be nice to easily create your own to get started along with adding custom nodes within Solution.

The community toolkit also does not currently have this feature.

See VsixCommunity/Community.VisualStudio.Toolkit#301

Are projection buffers still supported in VS 2022?

I can't make them work in my extension or the tutorial:
https://developercommunity.visualstudio.com/t/Projection-buffer-shows-full-document-in/1510793?from=email&viewtype=all

Is the plan to open-source this repo similar to Community Toolkit or will it only be NuGet reference(s) like older model? Just curious.

Please include Visualizers in the new Extension API as you guys build it out.

• Visualizers are not part of the existing extension model
• They use a horribly dated API that requires you to mark the types that will use the Visualizer
• Distributing them is a nightmare

The lack of a good extension model for Visualizers is currently Visual Studios achilles heel, in my opinion. Being able to better visualize data while debugging is critical to C#/.NET/Visual Studio being comparable to other languages and development environments.

There appears to be some differences in the example walkthrough and sample code project.

In the walkthrough, there is a CommandName variable that is not defined in the ExecuteCommandAsync method.

this.traceSource.TraceInformation($"Executing command {CommandName}");

In the final sample code file, it is defined here.

It seems like the property Name could be exposed similar to Id.

Great stuff and looking forward to it!

Understanding this is new and long-term project, somebody has to ask... When will we see a roadmap and possible timeline on certain features? For example, when will support come for Output Window and Solution Explorer?

Thanks

This might be specific to the current DGML Editor but adding here as the related APIs/docs could be improved as the new VS Extensibility roadmap progresses.

I currently use OpenSoftware DGML Builder as it is easier to work with compared to the provided VS GraphModel package. It seems like there could be improvements with the VS package including documentation on how to use (like serialization, code generation, use-cases, etc.).

It would also be nice to add extensibility (if not already) to the DGML Editor where commands, events, and other entry points can be used. For example, I would like to be able to add custom Context Menus to Nodes/Items in the graph.

I'm not sure if completely related, but improvements might also help the Visualizer issue along the way.

Thanks for reviewing. 😄

It seems that when you build a solution that contains projects with package references with the latest MSBuild it fails because the references are not passed to the Roslyn compiler. Here is an example commandline:

msbuild VSIXProject1.sln /p:Configuration=Release;Platform="Any CPU"

This works with the MSBuild form Visual Studio 2019. Is there something that I have missed here or there is an issue? This can be reproduced with a standard VSIX project created in Visual Studio 2022.

Is the CMake C++ integration within Visual Studio implemented through the public Open Folder extensibility API? I was assuming so and that the code would be on Github somewhere, but I wasn't able to find anything.

I've started work on an Open Folder extension for the build2 toolchain, but the lack of any example code is a major blocker on progress. If the CMake integration implementation was publicly available, it would be a huge help for this and similar projects. Is there any chance of that, or something similar?

Our extension makes heavy use of Roslyn. After migrating to Dev17, we see that MSBuildWorkspace.OpenProjectAsync is failing. It reports a diagnostic saying "The SDK 'Microsoft.NET.Sdk' specified could not be found."

We can actually repro this outside of our extension with a minimal Roslyn console app that tries to open a minimal C# class library project.

Here is the console app:

        static async Task Main(string[] args)
        {
            using (var workspace = MSBuildWorkspace.Create())
            {
                var project = await workspace.OpenProjectAsync(... filePath...);

                var diagnostics = workspace.Diagnostics;
           }
        }

Here is the project file for that app:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.Build" Version="16.10.0" />
    <PackageReference Include="Microsoft.Build.Framework" Version="16.10.0" />
    <PackageReference Include="Microsoft.Build.Tasks.Core" Version="16.10.0" />
    <PackageReference Include="Microsoft.CodeAnalysis" Version="4.0.0-1.final" />
    <PackageReference Include="Microsoft.CodeAnalysis.Workspaces.MSBuild" Version="4.0.0-1.final" />
  </ItemGroup>
  
</Project>

And, here is the class library project file we're trying to load. It has only a single Class1.cs generated by the New Project Wizard:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>

</Project>

Thanks very much in advance.

Will CommandIconAttribute eventually get an overload to include KnownMonikers or will it only be available via string? Would be a nice-to-have to do something like the following, but I guess you'd have to reference the additional Microsoft.VisualStudio.ImageCatalog package.

[CommandIcon(KnownMonikers.Extension, IconSettings.IconAndText)]

Hello,

Don’t sure it’s proper place for this question.

In order to be able to fix unexpected exceptions in our extension, we would like to send unhandled exception stack traces to remote logging service.

How could we configure the extension to catch all unhandled exceptions and send them to that service.

Thanks for your help!

Best regards,
Alex

C:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\Tools\LaunchDevCmd.bat

@TITLE Developer Command Prompt for VS 2019
@%comspec% /k " cd /d "%~dp0..\.." & "%~dp0vsdevcmd.bat" "

This might be on purpose so you don't have to rebrand everything until it is finalized, but I see other places where the version is listed as 2022.

Hi team,

It seems that in the Visual Studio 2022 preview 4 Microsoft.VisualStudio.TextTemplating.15.dll is renamed to Microsoft.VisualStudio.TextTemplating.dll. However, when we use Microsoft.VisualStudio.SDK (17.0.0-previews-1-31325-273) package reference we end up with а transitive reference to Microsoft.VisualStudio.TextTemplating.15. That's why the extension fails runtime in Visual Studio 2022.

Can you confirm this? And if so, can we expect a fix in Microsoft.VisualStudio.SDK package?

I didn't find any discussion about the Visual Studio 2022 new icons gallery (16x16, 32x32...),
is it available somewhere?

The wiki says:

You can also mark the extension as 'preview'...

How? Is it a tag? Something in the .vsixmanifest or something in the publishing manifest?

Following the instructions at https://github.com/microsoft/VSExtensibility/wiki/No-Code-Extensions, but it seems that the <ProductArchitecture> element isn't recognized. When I add those elements, I'm getting this error:

23>VSSDK : error VSSDK1062: Schema validation error for 'D:\Source\Repos\ProjectReunion\dev\VSIX\BuildOutput\obj\AnyCPUDebug\ProjectReunion.Extension\net472\extension.vsixmanifest'. The element 'PackageManifest' in namespace 'http://schemas.microsoft.com/developer/vsx-schema/2011' has invalid child element 'InstallationTarget' in namespace 'http://schemas.microsoft.com/developer/vsx-schema/2011'. List of possible elements expected: 'Metadata, Installation, Dependencies, Assets, Prerequisites, Installer' in namespace 'http://schemas.microsoft.com/developer/vsx-schema/2011' as well as any element in namespace '##other'.
23>VSSDK : error VSSDK1062: Schema validation error for 'D:\Source\Repos\ProjectReunion\dev\VSIX\BuildOutput\obj\AnyCPUDebug\ProjectReunion.Extension\net472\extension.vsixmanifest'. The 'http://schemas.microsoft.com/developer/vsx-schema/2011:Dependencies' element is not declared.
23>VSSDK : error VSSDK1062: Schema validation error for 'D:\Source\Repos\ProjectReunion\dev\VSIX\BuildOutput\obj\AnyCPUDebug\ProjectReunion.Extension\net472\extension.vsixmanifest'. The 'http://schemas.microsoft.com/developer/vsx-schema/2011:Assets' element is not declared.

This is attempting to build in VS2019. I tried building with the Dev17 preview, and it somehow fails to resolve Microsoft.VisualStudio.CoreUtility.

In the current version (17.0.0 Preview 1.0) of Visual Studio the VSIX Project template has a package reference to Microsoft.VSSDK.BuildTools version 17.0.1597 which is not available in nuget.org.

Currently the samples show you how to add a combobox or other toolbar item. Right now the user has to right click the toolbar and select the appropriate menu option to then display the toolbar item.
But how can you make that item appear in the toolbar automagically, when your extension is loaded for the very 1st time, for your specific project type?
A sample showing this would be great!

https://www.nuget.org/packages/Microsoft.VisualStudio.SDK

Visual Studio 2022 Preview 2 is now publicly available but the latest version of the MS.VS.SDK package is 17.0 Preview 1. When will the Preview 2 version be available for us to consume in our extensions?

I followed the documentation on how to create separated versions of my VSIX to target VS2019 and VS2022. It worked for me flawlessly, or at least that what I thought. Lately, when trying to install the 2019 version on another machine, I get errors when opening VS2019 when it tries to load the extension. Investigating the logs I found that it tries to load Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0. Investigating it further, it seems like the VSIX installer picked the 2022 version from somewhere, so files like catalog.json and manifest.json in the actual installation show Microsoft.VisualStudio.Component.CoreEditor dependency with version range [17.0,18.0) instead of [16.0,17.0) and extension.vsixmanifest is identical to the one in the 2022 version.
IIUC, this comes from C:\ProgramData\Microsoft\VisualStudio\Packages cache.

Does source.extension.vsixmanifest of the 2022 version must use different Identity Id than the 2019 version so the cache wouldn't be confused by it? If so, I think the documentation should mention it explicitly.

Building our extension with only the following two package references leads to a version conflict warning that seems to be caused by Microsoft.VisualStudio.TextTemplating.15.0.dll having a dependency on version 4.0.0.0 of Microsoft.CodeAnalysis.dll.

    <PackageReference Include="Microsoft.CodeAnalysis" Version="3.11.0-1.final" />
    <PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.0.0-previews-1-31410-273" />

References which depend on "Microsoft.CodeAnalysis, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" [].
    C:\Users\Kirk\.nuget\packages\microsoft.visualstudio.texttemplating.15.0\17.0.0-previews-1-31410-258\lib\net45\Microsoft.VisualStudio.TextTemplating.15.0.dll

I've upgraded my extension to 2022, and visual studio finds it and I can step into it.
However, During runtime I get this message box:
image
Is this related?

@BertanAygun

Member
BertanAygun commented 7 days ago
@ssemon, can you confirm if you also updated the ProjectSystem.Sdk package as mentioned above? This sounds like a mismatch of package versions.

Hi, I'm rewriting one of my extensions (https://github.com/LaggAt/ActivityWatchVS) to get used to the new out-of-process model. I really like the simplicity of that, and I know it is a work in progress.

As I cannot find something - is there some way to persist options and/or add an page to the options dialog?
This is the missing part to re-implement all functionality.

Thanks in advance.

The extension I am working on also runs on VS 2015. Is there any backward compatibility for that, or do I need to have a different VSIX?