From f1c4a69c3a33af8070fcf53764d59aa644429d53 Mon Sep 17 00:00:00 2001
From: "calvin@codingwithcalvin.net" <calvin@codingwithcalvin.net>
Date: Tue, 30 Dec 2025 16:49:09 -0500
Subject: [PATCH 1/2] feat(sdk): add implicit Microsoft.VSSDK.BuildTools
 package reference

- SDK now automatically includes VSSDK.BuildTools (version 17.* by default)
- Users can override version with VssdkBuildToolsVersion property
- Update README to remove explicit BuildTools references from examples
---
 README.md                                       |  5 ++---
 src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.props | 12 ++++++++++++
 2 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index cb40b46..26355da 100644
--- a/README.md
+++ b/README.md
@@ -105,7 +105,6 @@ Replace your entire `.csproj` file with the SDK-style format:
 
   <ItemGroup>
     <PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.*" />
-    <PackageReference Include="Microsoft.VSSDK.BuildTools" Version="17.*" PrivateAssets="all" />
   </ItemGroup>
 
 </Project>
@@ -138,11 +137,12 @@ Convert from `packages.config` to `PackageReference` format in your `.csproj`:
 ```xml
 <ItemGroup>
   <PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.*" />
-  <PackageReference Include="Microsoft.VSSDK.BuildTools" Version="17.*" PrivateAssets="all" />
   <!-- Add other packages your extension uses -->
 </ItemGroup>
 ```
 
+> **Note:** `Microsoft.VSSDK.BuildTools` is automatically included by the SDK.
+
 #### Step 6: Handle VSCT Files
 
 If you have `.vsct` files, they're automatically included. Remove any explicit `<VSCTCompile>` items unless you need custom metadata.
@@ -182,7 +182,6 @@ If you prefer to set up manually, create a `.csproj` file:
 
   <ItemGroup>
     <PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.*" />
-    <PackageReference Include="Microsoft.VSSDK.BuildTools" Version="17.*" PrivateAssets="all" />
   </ItemGroup>
 
 </Project>
diff --git a/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.props b/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.props
index f6b3ae6..5ae0c77 100644
--- a/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.props
+++ b/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.props
@@ -14,6 +14,18 @@
               Condition="Exists('$(MSBuildThisFileDirectory)..\analyzers\dotnet\cs\CodingWithCalvin.VsixSdk.Generators.dll')" />
   </ItemGroup>
 
+  <!--
+    Implicit package references for VSIX development.
+    Users can override the version by setting VssdkBuildToolsVersion before SDK import.
+  -->
+  <PropertyGroup>
+    <VssdkBuildToolsVersion Condition="'$(VssdkBuildToolsVersion)' == ''">17.*</VssdkBuildToolsVersion>
+  </PropertyGroup>
+
+  <ItemGroup>
+    <PackageReference Include="Microsoft.VSSDK.BuildTools" Version="$(VssdkBuildToolsVersion)" PrivateAssets="all" />
+  </ItemGroup>
+
   <PropertyGroup>
     <!-- Identify that this SDK is in use -->
     <UsingCodingWithCalvinVsixSdk>true</UsingCodingWithCalvinVsixSdk>

From ed439899622e8096b7cf78686e37b3683f8348ea Mon Sep 17 00:00:00 2001
From: "calvin@codingwithcalvin.net" <calvin@codingwithcalvin.net>
Date: Tue, 30 Dec 2025 17:48:32 -0500
Subject: [PATCH 2/2] feat(sdk): auto-generate launchSettings.json for F5
 debugging

When building inside Visual Studio for the first time, the SDK now
generates Properties/launchSettings.json with a profile that launches
devenv.exe with /rootSuffix Exp. This enables F5 debugging out of the
box without any manual configuration.
---
 .../Sdk/Sdk.Vsix.targets                      | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.targets b/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.targets
index 59fb014..b914728 100644
--- a/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.targets
+++ b/src/CodingWithCalvin.VsixSdk/Sdk/Sdk.Vsix.targets
@@ -205,6 +205,35 @@
              Text="No .vsixmanifest file found. VSIX projects require a manifest file." />
   </Target>
 
+  <!--
+    Generate launchSettings.json for F5 debugging
+    Only runs when building inside Visual Studio and the file doesn't exist
+    This configures VS to launch devenv.exe with the experimental instance
+  -->
+  <Target Name="GenerateLaunchSettings"
+          BeforeTargets="BeforeBuild"
+          Condition="'$(BuildingInsideVisualStudio)' == 'true' and '$(DevEnvDir)' != '' and !Exists('$(MSBuildProjectDirectory)\Properties\launchSettings.json')">
+
+    <PropertyGroup>
+      <_LaunchSettingsContent><![CDATA[{
+  "profiles": {
+    "Start Experimental Instance": {
+      "commandName": "Executable",
+      "executablePath": "$(DevEnvDir)devenv.exe",
+      "commandLineArgs": "/rootSuffix Exp"
+    }
+  }
+}]]></_LaunchSettingsContent>
+    </PropertyGroup>
+
+    <MakeDir Directories="$(MSBuildProjectDirectory)\Properties" Condition="!Exists('$(MSBuildProjectDirectory)\Properties')" />
+    <WriteLinesToFile File="$(MSBuildProjectDirectory)\Properties\launchSettings.json"
+                      Lines="$(_LaunchSettingsContent)"
+                      Overwrite="true" />
+
+    <Message Importance="high" Text="Generated Properties/launchSettings.json for F5 debugging" />
+  </Target>
+
   <!--
     Import VSSDK targets if available
     This is the key integration point with Microsoft.VSSDK.BuildTools