Merge branch 'single-file-release' into 'master'

Change build to single file release

See merge request !30

README.md

@@ -12,7 +12,7 @@ Using the .NET SDK command `dotnet`: Execute `dotnet run --project ./src/SparseT
 
 > Make sure you specify the `SparseTransform.CLI` project as the library project is not runnable by itself.
 
-## How to Build the Program
+## How to Build the Program Into an Executable
 
 > The instructions below assume that your working directory is at the project root
 
@@ -21,16 +21,18 @@ Using the .NET SDK command `dotnet` you can choose between building for executio
 ### Using .NET Framework:
 
 ```
-dotnet build ./src/SparseTransform.CLI/SparseTransform.CLI.csproj --configuration Release
+dotnet publish ./src/SparseTransform.CLI/SparseTransform.CLI.csproj -r <RID> -o SparseTransform --self-contained false
 ```
 
 ### As a Standalone Executable: 
 
 ```
-dotnet build ./src/SparseTransform.CLI/SparseTransform.CLI.csproj --runtime <RID> --self-contained --configuration Release
+dotnet publish ./src/SparseTransform.CLI/SparseTransform.CLI.csproj -r <RID> -o SparseTransform
 ```
 
-\<RID> specifies the Runtime-ID that you want to build for. For available options see the [.NET RID Catalog](https://docs.microsoft.com/en-us/dotnet/core/rid-catalog)
+\<RID> specifies the Runtime-ID that you want to build for (e.g. win-x64 or linux-x64). For available options see the [.NET RID Catalog](https://docs.microsoft.com/en-us/dotnet/core/rid-catalog).
+
+Both commands output to the SparseTransform directory at the project root. The output path can be changed as desired.
 
 ## How to Build the Documentation
 

src/SparseTransform.CLI/SparseTransform.CLI.csproj

@@ -13,6 +13,7 @@
     <TargetFramework>net6.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
+    <PublishSingleFile>true</PublishSingleFile>
   </PropertyGroup>
 
 </Project>