![]() If I go to a command line and type dotnet -version it will tell me the SDK version I'm currently running, which will be the preview version I just installed: What version of the SDK am I currently running? But now we need to know how to identify which one of these SDKs is currently active, and how to switch between them. So that's great, I've got the 2.1 preview SDK and runtime available on my machine, and I can experiment with it. Inside the C:\Program Files\dotnet\shared\ folder we can see all the versions of the runtime I've installed, including the 2.1.0 preview that came with the SDK: NET Core SDK versions I've got installed on this PC:Īnd the same is true for the. So when I install the preview, all that happens is that I get a new folder under C:\Program Files\dotnet\sdk. NET Core SDKs are installed side by side, so will not modify any previous SDK installations. NET Core SDK break something?, and second, can I easily switch back to the release version of the SDK? So I had two key questions before I was ready to pull the trigger. So I've worked out that I need 2.1.300-preview1, but like many developers, I've been burned in the past by installing bad preview bits that mess up my development machine. Will bad things happen if I install a preview SDK? ![]() Confusingly the 2.1.103 SDK actually contains the 2.0 runtime (not 2.1)! There's a new versioning strategy going forwards that will make the relationship between runtime and SDK easier to understand, but before that, the runtime and SDK version numbers did not necessarily correspond. The one called 2.1.300-preview1 is the one I wanted - that's the SDK for the. That's right, there's two 2.1 SDK's available. NET homepage (found at the easy to remember ), and navigated to the all downloads page, I must confess to being a little confused by the experience. Which SDK do I need?īut when I visited the. NET Core 2.1, so that I could experiment a bit with the new Span functionality, which is something I'm very excited about. I recently wanted to try out the preview of.
0 Comments
Leave a Reply. |