Style and doc updates (#164)

Author: craigktreasure

.editorconfig

@@ -51,6 +51,9 @@ dotnet_diagnostic.IDE0008.severity = error
 # IDE0021: Use expression body for constructors
 dotnet_diagnostic.IDE0021.severity = suggestion
 
+# IDE0022: Use expression body for methods
+dotnet_diagnostic.IDE0022.severity = suggestion
+
 # IDE0046: Use conditional expression for return
 dotnet_diagnostic.IDE0046.severity = suggestion
 

Docs/BuildingAndTesting.md

@@ -4,15 +4,15 @@
 
 ### Using Visual Studio
 
-* [Visual Studio 2022 17+](https://visualstudio.microsoft.com/downloads/)
-  * Visual Studio 2022 comes with the .NET 6 SDK, you can also install another
-    version from [here](https://dotnet.microsoft.com/download/dotnet/6.0).
+* [Visual Studio 2022 17.4+][download-vs]
+  * You'll also need the [.NET 6 SDK][download-dotnet-6-sdk] and [.NET 7 SDK][download-dotnet-7-sdk].
 
 ### Visual Studio Code
 
-* [Visual Studio Code](https://code.visualstudio.com/Download)
+* [Visual Studio Code][download-vs-code]
   * Install recommended extensions.
-* [.NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0)
+* [.NET 6 SDK][download-dotnet-6-sdk]
+* [.NET 7 SDK][download-dotnet-7-sdk]
 
 ## Build the tool
 
@@ -32,7 +32,7 @@ To run all the tests, simply run the following command:
 dotnet test
 ```
 
-## Managing a tool instalation from local build output
+## Managing a tool installation from local build output
 
 ### Install the tool
 
@@ -54,7 +54,7 @@ For stable release versions, run the following command:
 dotnet tool update -g SlnUp --add-source ./__packages/NuGet/Release/
 ```
 
-For pre-release versions, there is currently no way to update to a pre-release version. See [here](https://github.com/dotnet/sdk/issues/2551) for updates on this issue. For the time being, you need to [uninstall](#uninstall-the-tool) the previous version of the tool and then [install](#install-the-tool) the tool again.
+For pre-release versions, you need to specify the `--prerelase` argument.
 
 ### Uninstall the tool
 
@@ -75,3 +75,8 @@ Simply run the following PowerShell script:
 ```powershell
 ./scripts/UpdateVSVersions.ps1
 ```
+
+[download-dotnet-6-sdk]: https://dotnet.microsoft.com/download/dotnet/6.0 "Download .NET 6.0"
+[download-dotnet-7-sdk]: https://dotnet.microsoft.com/download/dotnet/7.0 "Download .NET 7.0"
+[download-vs]: https://visualstudio.microsoft.com/downloads/ "Download Visual Studio"
+[download-vs-code]: https://code.visualstudio.com/Download "Download Visual Studio Code"

README.md

@@ -22,8 +22,8 @@ solution file using a Visual Studio version number.
 
 The Visual Studio Version Selector tool, which determines which version of
 Visual Studio to open when you double-click a .sln file, uses the solution
-[file header](https://docs.microsoft.com/visualstudio/extensibility/internals/solution-dot-sln-file?view=vs-2022#file-header)
-to determine which version of Visual Studio to open.
+[file header][vs-sln-file-header] to determine which version of Visual Studio
+to open.
 
 Updating a solution file with correct version information requires you to
 understand the solution file header and the Visual Studio version information.
@@ -89,16 +89,15 @@ slnup 17.0 --build-version 17.0.31903.59
 
 ## How does it work?
 
-Visual Studio solution files have a well known
-[file header](https://docs.microsoft.com/visualstudio/extensibility/internals/solution-dot-sln-file?view=vs-2022#file-header).
+Visual Studio solution files have a well known [file header][vs-sln-file-header].
 The tool knows how to parse and update the solution file header and save the
 file. The tool also knows version information for builds of Visual Studio from
 Visual Studio 2017 to 2022. The version information specified, is used to update
 the file header.
 
 Consider a solution file with the following file header:
 
-```
+```text
 Microsoft Visual Studio Solution File, Format Version 12.00
 # Visual Studio Version 16
 VisualStudioVersion = 16.0.28701.123
@@ -125,7 +124,7 @@ In the case of `2022`, the tool will use the latest known version information
 it knows for that version. So, this would cause the tool to update the solution
 file header to the following:
 
-```
+```text
 Microsoft Visual Studio Solution File, Format Version 12.00
 # Visual Studio Version 17
 VisualStudioVersion = 17.0.31903.59
@@ -146,3 +145,5 @@ Visual Studio 2022.
     `MinimumVisualStudioVersion = 10.0.40219.1`, then those values will be added
     to the file header.
 - The tool supports Visual Studio 2017, 2019, and 2022.
+
+[vs-sln-file-header]: https://docs.microsoft.com/visualstudio/extensibility/internals/solution-dot-sln-file?view=vs-2022#file-header "File header"

tests/.editorconfig

@@ -4,6 +4,3 @@
 
 # CA1707: Identifiers should not contain underscores
 dotnet_diagnostic.CA1707.severity = none
-
-# IDE0022: Use expression body for methods
-dotnet_diagnostic.IDE0022.severity = suggestion