It’s been a few years since I last used .net so I thought I’d give it a go. It was slightly more eventful 30 minutes than I’d have liked, so I thought I’d write it up.
I started by trying to install Visual Studio, but half an hour later it was still under 50% done, and since I only wanted to be writing scripts rather than applications, I started looking for some smaller getting started guides and came across Microsoft’s guide to getting started with .NET Core. So I took a brief look at the new shape of the .NET stack, liked what I saw, and went back to the guide.
After installing the .NET Version Manager (dnvm) I had to restart PowerShell to get the changes to my PATH to take effect, and also I had to open an Administrator PowerShell window and run
set-executionpolicy remotesigned because I hit the
Running scripts is disabled on this system error message.
I’d closed my PowerShell window by this point, and when I opened a new one and ran
dnu restore I got an error message about it not being on my path (
The term ‘dnu’ is not recognized as the name of a cmdlet, function, script file, or operable program.). Running
dnvm upgrade seems to have fixed this and I can now run the commands from both PowerShell and Command Prompt!
My “Hello World” did at least run first time. Phew!
I should now have the infrastructure to get properly going, but this was a much rougher intro than I was hoping for.