Remove brittle active document tracking

The workarounds to access the running document table was brittle, caused VS to fail to exit sometimes (hanging on the MSBuild process), etc.

So we'll just keep the MSBuild-only part of generating the launch profiles for each top-level file and honoring the user's selection for Run.

Author: kzu

SmallSharp.sln

@@ -17,7 +17,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "workflows", "workflows", "{
 		.github\workflows\publish.yml = .github\workflows\publish.yml
 	EndProjectSection
 EndProject
-Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "SmallSharp", "src\SmallSharp\SmallSharp.csproj", "{97648980-AA30-4AC0-B8E9-FCF6359F56A0}"
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "SmallSharp", "src\SmallSharp\SmallSharp.msbuildproj", "{97648980-AA30-4AC0-B8E9-FCF6359F56A0}"
 EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution

readme.md

@@ -3,14 +3,12 @@
 
 [![Version](https://img.shields.io/nuget/v/SmallSharp.svg?color=royalblue)](https://www.nuget.org/packages/SmallSharp) [![Downloads](https://img.shields.io/nuget/dt/SmallSharp?color=darkmagenta)](https://www.nuget.org/packages/SmallSharp) [![License](https://img.shields.io/github/license/devlooped/SmallSharp.svg?color=blue)](https://github.com/devlooped/SmallSharp/blob/main/LICENSE) [![GH CI Status](https://github.com/devlooped/SmallSharp/workflows/build/badge.svg?branch=main)](https://github.com/devlooped/avatar/actions?query=branch%3Amain+workflow%3Abuild+) 
 
-![Icon](https://raw.githubusercontent.com/devlooped/SmallSharp/main/assets/img/SmallSharpDemo.gif)
-
 <!-- #content -->
 Create, edit and run multiple C# top-level programs in the same project 😍
 
 ## Why
 
-The new-ish C# [top-level programs](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/program-structure/top-level-statements) 
+C# [top-level programs](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/program-structure/top-level-statements) 
 allow a very intuitive, simple and streamlined experience for quickly spiking or learning C#. 
 
 One missing thing since their introduction in Visual Studio is that you can only have one such 
@@ -41,17 +39,14 @@ There is no need to install any Visual Studio extension. SmallSharp works by jus
 
 ![New Project Dialog](https://raw.githubusercontent.com/devlooped/SmallSharp/main/assets/img/NewConsoleProject.png)
 
-   By default, this new console project may not be set up to target `net5.0` or use the latest C# version. 
-   So click on the project node, and the project file will open in the editor. Make sure you either:
-
-  * Target the recommended framework version (i.e. net6.0):
+  * Target the recommended framework version (i.e. net8.0 or net10.0):
 
 ```xml
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
     <OutputType>Exe</OutputType>
-    <TargetFramework>net6.0</TargetFramework>
+    <TargetFramework>net8.0</TargetFramework>
   </PropertyGroup>
 
 </Project>
@@ -107,15 +102,12 @@ WriteLine("Hello World!");
 ```
 
 Keep adding as many top-level programs as you need, and switch between them easily by simply 
-changing the active document.
-
-![Demo](https://raw.githubusercontent.com/devlooped/SmallSharp/main/assets/img/TrackSelection.gif)
-
+selecting the desired file from the Start button dropdown.
 
 ## How It Works
 
 This nuget package leverages in concert the following standalone and otherwise 
-unrelated features of the compiler, nuget, Visual Studio and MSBuild:
+unrelated features of the compiler, nuget and MSBuild:
 
 1. The C# compiler only allows one top-level program per compilation.
 2. Launch profiles (the entries in the Run dropdown) are populated from the Properties\launchSettings.json file
@@ -127,8 +119,7 @@ unrelated features of the compiler, nuget, Visual Studio and MSBuild:
 
 Using the above features in concert, **SmallSharp** essentially does the following:
 
-* Monitor the active document in VS and emit it as a `launchSettings.json` profile and set it as 
-   the `$(ActiveDebugProfile)`.
+* Emit top-level files as a `launchSettings.json` profile and set the `$(ActiveDebugProfile)`.
 
 * Exclude `.cs` files at the project level from being included as `<Compile>` by the default SDK 
   includes and include them explicitly as `<None>` instead so they show up in the solution explorer. 
@@ -139,16 +130,6 @@ Using the above features in concert, **SmallSharp** essentially does the followi
 This basically mean that this it will also work consistently if you use `dotnet run` from the command-line, 
 since the "Main" file selection is performed exclusively via MSBuild item manipulation.
 
-Finally, there is some lovely COM-based magic to access the active Visual Studio IDE (via DTE) to monitor 
-the currently opened source file to keep it in sync with the launch profile. This is done purely using 
-public COM primitives and equally public VSSDK nuget packages their APIs. This enables some useful integration 
-with the IDE without requiring installing a VS extension from the marketplace and deal with gracefully 
-degrading functionality.
-
-> NOTE: If active document tracking fails to initialize properly restarting Visual Studio will almost 
-> always fix it. Once tracking starts, it will work consistently from that point on. The Start dropdown 
-> is always available as a fallback in case of issues.
-
 <!-- include https://github.com/devlooped/sponsors/raw/main/footer.md -->
 # Sponsors