Bump to v0.2.0

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## 0.2.0
+
+#### Install natively using dotnet-install scripts
+
+Having an installation for each .NET SDK version causes all sorts of
+issues, as the whole ecosystem expects all SDKs and runtimes to share
+the same installation directory.
+
+In practice this is currently causing issues because DOTNET_ROOT cannot
+be set to anything meaningful on a system-level. Other tooling like
+IntelliJ Rider can thus not find the correct SDK to use. You'd have to
+somehow set DOTNET_ROOT per project, and even then that project can only
+be aware of a single SDK version at a time.
+
+So I've decided to rely on proto's `native_install` feature instead,
+which opens another can of worms, but a more manageable one at least.
+It relies on the official dotnet-install scripts to install SDKs into
+whatever DOTNET_ROOT is set to (or ~/.dotnet per default).
+Supporting uninstallation will come later, as it will be a bit tricky,
+now that everything lives in the same directory.
+
+The dotnet executable will no longer be shimmed nor symlinked, and the
+user is expected to add DOTNET_ROOT to their PATH.
+
 ## 0.1.0
 
 #### global.json detection

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "dotnet_plugin"
-version = "0.1.0"
+version = "0.2.0"
 edition = "2021"
 license = "MIT"
 publish = false

README.md

@@ -18,6 +18,11 @@ Or preferably pin a specific version, to avoid nasty surprises if we mess up a r
 dotnet = "source:https://github.com/Phault/proto-dotnet-plugin/releases/download/vX.Y.Z/dotnet_plugin.wasm"
 ```
 
+This plugin relies on two assumptions:
+
+- As the SDKs will be installed to the location your `DOTNET_ROOT` environment variable points to, it **must** be a user-writable location. This is usually `~/.dotnet` which is also the default location if the variable is not defined.
+- The location for your `DOTNET_ROOT` must be in your `PATH`, as we do not shim or symlink it like other proto plugins.
+
 ## Usage
 
 ```shell