Convert sdk.sln to slnx

Author: kasperk81

TemplateEngine.slnf

@@ -1,6 +1,6 @@
 {
   "solution": {
-    "path": "sdk.sln",
+    "path": "sdk.slnx",
     "projects": [
       "test\\TestAssets\\TestPackages\\dotnet-new\\Microsoft.TemplateEngine.TestTemplates.csproj",
       "src\\Cli\\Microsoft.DotNet.Cli.Sln.Internal\\Microsoft.DotNet.Cli.Sln.Internal.csproj",
@@ -21,4 +21,4 @@
       "template_feed\\Microsoft.DotNet.Common.ProjectTemplates.10.0\\Microsoft.DotNet.Common.ProjectTemplates.10.0.csproj"
     ]
   }
-}
+}

containers.slnf

@@ -1,6 +1,6 @@
 {
   "solution": {
-    "path": "sdk.sln",
+    "path": "sdk.slnx",
     "projects": [
       "src\\Cli\\Microsoft.DotNet.Cli.Utils\\Microsoft.DotNet.Cli.Utils.csproj",
       "src\\Cli\\Microsoft.DotNet.InternalAbstractions\\Microsoft.DotNet.InternalAbstractions.csproj",
@@ -13,4 +13,4 @@
       "test\\containerize.UnitTests\\containerize.UnitTests.csproj"
     ]
   }
-}
+}

documentation/project-docs/developer-guide.md

@@ -34,9 +34,9 @@ As part of the build, some intermediate files will get generated which may run i
 
 #### Using Visual Studio
 
-The simple way to launch Visual Studio after building via `build.cmd` is to double-click the `VS with sdk.sln` Windows shortcut in the `artifacts` folder. This will load the generated environment automatically and launch Visual Studio with the `sdk.sln` solution.
+The simple way to launch Visual Studio after building via `build.cmd` is to double-click the `VS with sdk.slnx` Windows shortcut in the `artifacts` folder. This will load the generated environment automatically and launch Visual Studio with the `sdk.slnx` solution.
 
-Alternatively, to open the solution in Visual Studio, be sure to build with `build.cmd` and run the generated environment for your shell. If you're using `cmd`, then run `artifacts\sdk-build-env.bat`. If you're using PowerShell, you need to 'dot source' `artifacts/sdk-build-env.ps1`. Finally, open Visual Studio with `devenv sdk.sln`.
+Alternatively, to open the solution in Visual Studio, be sure to build with `build.cmd` and run the generated environment for your shell. If you're using `cmd`, then run `artifacts\sdk-build-env.bat`. If you're using PowerShell, you need to 'dot source' `artifacts/sdk-build-env.ps1`. Finally, open Visual Studio with `devenv sdk.slnx`.
 
 In addition, Visual Studio must have the following option set (this option is automatically set in preview Visual Studio builds):
 
@@ -79,7 +79,7 @@ Run the following command from the root of the repository to run all the .NET Co
 
 The `dotnet` executable in the artifacts directory can be run directly.
 
-However, it's easier to configure a test environment to run the built `dotnet`. This test environment is managed by dogfood. 
+However, it's easier to configure a test environment to run the built `dotnet`. This test environment is managed by dogfood.
 The dogfood script starts a new Powershell with the environment configured to redirect SDK resolution to your build.
 
 From that shell your SDK will be available in:
@@ -146,7 +146,7 @@ Use developer command prompt for Visual Studio or put devenv on you PATH
 ```shell
 build.cmd # to have a full build first
 .\artifacts\sdk-build-env.bat
-devenv sdk.sln
+devenv sdk.slnx
 ```
 
 Note again that in Visual studio "Use previews of the .NET SDK (requires restart)" must be checked. See the above comment for how to enable this.

eng/dotnet-format/dotnet-format-integration.yml

@@ -17,7 +17,7 @@ parameters:
   - Name: sdk
     _repo: "https://github.com/dotnet/sdk"
     _repoName: "dotnet/sdk"
-    _targetSolution: "sdk.sln"
+    _targetSolution: "sdk.slnx"
     _branchName: "main"
     _sha: "be25db95c376bffd508a023399ddd34392fe6458"
     _useParentSdk: 0

eng/restore-toolset.ps1

@@ -102,7 +102,7 @@ function CreateVSShortcut()
   }
 
   $scriptPath = Join-Path $ArtifactsDir 'sdk-build-env.ps1'
-  $slnPath = Join-Path $RepoRoot 'sdk.sln'
+  $slnPath = Join-Path $RepoRoot 'sdk.slnx'
   $commandToLaunch = "& '$scriptPath'; & '$devenvPath' '$slnPath'"
   $powershellPath = '%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe'
   $shortcutPath = Join-Path $ArtifactsDir 'VS with sdk.sln.lnk'

sdk.sln

@@ -1,6 +1,6 @@
 {
   "solution": {
-    "path": "sdk.sln",
+    "path": "sdk.slnx",
     "projects": [
       "src\\BlazorWasmSdk\\Tasks\\Microsoft.NET.Sdk.BlazorWebAssembly.Tasks.csproj",
       "src\\BlazorWasmSdk\\Tool\\Microsoft.NET.Sdk.BlazorWebAssembly.Tool.csproj",

sdk.slnx

@@ -1,6 +1,6 @@
 {
   "solution": {
-    "path": "..\\..\\sdk.sln",
+    "path": "..\\..\\sdk.slnx",
     "projects": [
       "src\\BlazorWasmSdk\\Tasks\\Microsoft.NET.Sdk.BlazorWebAssembly.Tasks.csproj",
       "src\\BlazorWasmSdk\\Tool\\Microsoft.NET.Sdk.BlazorWebAssembly.Tool.csproj",

source-build.slnf

@@ -1,9 +1,9 @@
 {
   "solution": {
-    "path": "..\\..\\sdk.sln",
+    "path": "..\\..\\sdk.slnx",
     "projects": [
       "src\\BuiltInTools\\dotnet-format\\dotnet-format.csproj",
       "test\\dotnet-format.UnitTests\\dotnet-format.UnitTests.csproj"
     ]
   }
-}
+}