Update in-proc documentation

Author: BertanAygun

docs/extensibility/visualstudio.extensibility/get-started/in-proc-extensions.md

@@ -10,15 +10,24 @@ manager: jmartens
 ms.technology: vs-ide-sdk
 ---
 
-# Create your first VSSDK-compatible VisualStudio.Extensibility extension
+# Using VisualStudio.Extensibility SDK and VSSDK together
 
-While the VisualStudio.Extensibility model was created primarily to host extensions outside of the devenv.exe process, starting with Visual Studio 2022 17.4 Preview 1 it's possible to build a VisualStudio.Extensibility extension that's hosted within devenv.exe and can use traditional extensibility APIs provided by the [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) packages.
+While the VisualStudio.Extensibility model was created primarily to host extensions outside of the devenv.exe process, it is possible to use VisualStudio.Extensibility SDK APIs in an extension running in Visual Studio process and utilizing traditional extensibility APIs provided by the [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) packages.
+
+The support of *in-proc* usage is meant to allow early adopters to the new VisualStudio.Extensibility APIs while relying on [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) to cover any feature gap.
+
+This document is a quick walkthrough on different options to utilize VisualStudio.Extensibility SDK in-proc.
+
+* If you are developing a new extension, our recommended method is to create a VisualStudio.Extension that is hosted in-process following [this tutorial](#create-your-first-vssdk-compatible-visualstudioextensibility-extension). This will allow you to use full capabilities of VisualStudio.Extensibility SDK in addition to being able to inject VSSDK and MEF services.
 
-The support of *in-proc* extensions is meant to allow early adopters to the new VisualStudio.Extensibility APIs while relying on [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) to cover any feature gap.
+* If you have an existing VSSDK extension, you can follow [these tips](#use-visualstudioextensibility-apis-from-existing-vssdk-extensions) to use the new `VisualStudioExtensibility` instance in your extension.
 
-At this time, VSIX extensions containing VisualStudio.Extensibility references can't be uploaded to the Visual Studio Marketplace due to VisualStudio.Extensibility being in preview status.
+* If you want to add commands, debug visualizers, tool windows to your existing VSSDK extension by using VisualStudio.Extensibility SDK, you can refer to [these tips](#using-visualstudioextensibility-sdk-and-vssdk-together) to host both a VSSDK extension and VisualStudio.Extensibility SDK in the same VS extension project.
+
+# Create your first VSSDK-compatible VisualStudio.Extensibility extension
+
+While the VisualStudio.Extensibility model was created primarily to host extensions outside of the devenv.exe process, starting with Visual Studio 2022 17.4 Preview 1 it's possible to build a VisualStudio.Extensibility extension that's hosted within devenv.exe and can use traditional extensibility APIs provided by the [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) packages.
 
-This document is a quick walkthrough on how to create your first VS-SDK-compatible extension using the VisualStudio.Extensibility model.
 
 ## Prerequisites
 
@@ -112,3 +121,60 @@ internal class MyExtension : Extension
 
     ...
 ```
+
+# Use VisualStudio.Extensibility from existing VSSDK extensions
+
+For existing VSSDK extension, another option is to query for `VisualStudioExtensibility` instance via service provider and utilize its methods. This method will allow you to use new API surface area of VisualStudio.Extensibility SDK in your existing components. This can be useful in situations where you like to use the new API to query project information, document management without creating a new VisualStudio.Extensibility based extension. 
+
+Here is an example code snippet that shows how one can utilize `VisualStudioExtensibility` with in a VSSDK package:
+
+* In your `.csproj` include a package reference to VisualStudio.Extensibility APIs:
+
+```XML
+  <ItemGroup>
+    <PackageReference Include="Microsoft.VisualStudio.Extensibility" Version="17.9.23-preview-1" />
+  </ItemGroup>
+```
+
+* You can now query for `VisualStudioExtensibility` instance via `GetServiceAsync` method in your package or other components:
+
+```CSharp
+...
+using Microsoft.VisualStudio.Extensibility;
+...
+
+public class VSSDKPackage : AsyncPackage
+{
+    protected override async Task InitializeAsync(CancellationToken cancellationToken, IProgress<ServiceProgressData> progress)
+    {
+        VisualStudioExtensibility extensibility = await this.GetServiceAsync<VisualStudioExtensibility, VisualStudioExtensibility>();
+        await extensibility.Shell().ShowPromptAsync("Hello from in-proc", PromptOptions.OK, cancellationToken);
+        ...
+    }
+}
+```
+
+# Add VisualStudio.Extensibility extension in to an existing VSSDK extension project
+
+If you also want to contribute components like tool windows, editor listeners using VisualStudio.Extensibility SDK within your existing VSSDK extension, you will have to follow additional steps to create a VisualStudio.Extensibility `Extension` instance in your project.
+
+* You will need an SDK style `.csproj` in order to utilize VisualStudio.Extensibility SDK packages. For existing projects, you may need to update your `.csproj` to an SDK style one.
+
+* Remove package reference for `Microsoft.VSSDK.BuildTools` and instead add package references for VisualStudio.Extensibility.
+
+```XML
+    <PackageReference Include="Microsoft.VisualStudio.Extensibility.Sdk" Version="17.9.23-preview-1" />
+    <PackageReference Include="Microsoft.VisualStudio.Extensibility.Build" Version="17.9.23-preview-1" />
+```
+
+* Add `VssdkCompatibleExtension` property to your project file, setting it to `true`. This will disable `vsixmanifest` generation and enable some of VSSDK features for compatibility.
+
+```XML
+<PropertyGroup>
+    <VssdkCompatibleExtension>true</VssdkCompatibleExtension>
+</PropertyGroup>    
+```
+
+* Create a new extension class inheriting from `Extension` base class and set [RequiresInProcessHosting](#requiresinprocesshosting-property) property as shown above.
+
+You can now use all capabilities of VisualStudio.Extensibility together with your existing VSSDK extension.

docs/extensibility/visualstudio.extensibility/visualstudio-extensibility.md

@@ -25,7 +25,7 @@ VisualStudio.Extensibility aims to address many of the problems developers exper
 * Simplified architecture, consistent APIs, and clear documentation
 * Extensions can be installed without restarting Visual Studio
 
-Eventually, you will be able to use the VisualStudio.Extensibility SDK to write any extension you could write using the VS SDK. However, until that time, you might encounter situations where the functionality you need in your extension isn't yet available in VisualStudio.Extensibility. In that case, you can develop an in-process extension by leveraging the new VisualStudio.Extensibility APIs while relying on VS SDK to cover any feature gap. To learn more, see [In-proc extensions](./get-started/in-proc-extensions.md).
+Eventually, you will be able to use the VisualStudio.Extensibility SDK to write any extension you could write using the VS SDK. However, until that time, you might encounter situations where the functionality you need in your extension isn't yet available in VisualStudio.Extensibility. In that case, you can use VisualStudio.Extensibility SDK together with VS SDK running in-process to cover any feature gap. To learn more, see [In-proc extensions](./get-started/in-proc-extensions.md).
 
 The latest information on VisualStudio.Extensibility may be found in the VSExtensibility GitHub repo at [announcements](https://github.com/microsoft/VSExtensibility/blob/main/docs/announcements.md).