Upgrading to v0.5.0

If you've used a version of dnvm before v0.5.0, things might be a bit different.

In previous releases, dnvm installed preview versions of the SDK to a separate directory by default. As of v0.5.0 this is no longer the default behavior. You can still do so using the -s flag, but all channels will now be installed to the default directory.

If you would like to make your existing setup match the new defaults you can follow these steps:

1. Untrack the preview channel using the dnvm untrack preview command.
2. Reinstall the preview channel using dnvm track preview. a. You may receive the error that the latest preview SDK is already installed in another directory. You can either use dnvm uninstall <version> to uninstall the existing SDK, or you can use the dnvm track preview -f command to force installation and duplicate the install in the dn directory.

The original reason for the change is that previews can sometimes cause downgrades of the installed release versions. There are two possible solutions:

1. Install previews to a separate directory and switch directories when using previews.
2. Use a global.json file in the repository to specify which SDK version to use.

dnvm previously used (1) but feedback was that it was too difficult to use. The new recommendation is to use (2) if you are publishing non-preview-versioned assets while installing previews on your machine.