DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Zero to AI Hero, Part 2: Understanding Plugins in Semantic Kernel, A Deep Dive With Examples
  • Beyond n8n for Workflow Automation: Agent Graphs as Your Universal Agent Harness
  • Implementing Effective Document Fraud Detection in C#
  • How To Build A White-label AI Chatbot: Here's the Complete Process

Trending

  • You Learned AI. So Why Are You Still Not Getting Hired?
  • AWS Managed Database Observability: Monitoring DynamoDB, ElastiCache, and Redshift Beyond CloudWatch
  • Why SAP S/4HANA Landscape Design Impacts Cloud TCO More Than Compute Costs
  • Chat with Your Oracle Database: SQLcl MCP + GitHub Copilot
  1. DZone
  2. Coding
  3. Languages
  4. Switching Between .NET Core SDK Versions

Switching Between .NET Core SDK Versions

If you're working with two different versions of .NET Core, you'll need two different SDKs. But this isn't as easy as it sounds.

By 
Faisal Pathan user avatar
Faisal Pathan
·
Feb. 22, 19 · Tutorial
Likes (4)
Comment
Save
Tweet
Share
113.0K Views

Join the DZone community and get the full member experience.

Join For Free

In this article, we’ll learn how we can switch between the versions of the .NET Core SDK as per our needs.

If you have worked on one project that used .NET Core version 2.1 and then you installed .NET Core 3.0 Preview, you will get an SDK error while trying to run your .NET Core 2.1 project. This is because your current SDK version has changed to 3.0

A big advantage of .NET Core is that it installs .NET Core SDKs separately, so the new SDK does not affect the previously installed SDK. You can see all the installed SDKs under "C:\Program Files\dotnet\sdk".

Switching Between .NET Core SDK Versions

First, we are going to see how we can view our current SDK version on the machine. By default, it will be the latest installed version (the SDK you installed at last).

To view your current SDK version, follow the below steps.

Open the command prompt and type the below command.

dotnet --version 

Switching Between .NET Core SDK Versions

To view all installed SDKs, follow the below steps.

Open the command prompt and execute the following command: dotnet --info. This will show the list of all available SDKs on your system.    

Switching Between .NET Core SDK Versions

Checking the Version of Your .NET Core Project

Open your project's source folder and, in the address bar, type "cmd" and press Enter. It will open the command prompt with the project path. Switching Between .NET Core SDK Versions

Execute the following command:  dotnet --version.Switching Between .NET Core SDK VersionsIt will display your project's current SDK version,i.e., 2.1.503 in our case. 

Now, we are going to change this version to Core 3.0. For that, type the below command and press Enter.

dotnet new globaljson --sdk-version 3.0.100-preview-010184 --force 

Switching Between .NET Core SDK Versions 

Switching Between .NET Core SDK Versions

It will create a "global.json" file which is stored in the folder of the current version of your project's SDK. 

{  
  "sdk": {  
    "version": "3.0.100-preview-010184"  
  }  
}

To create the "global.json" file in the current directory folder, you need to fire this command:  

dotnet new globaljson 

This will create a "global.json" file and, by default, it is set to the latest version.

Summary

Here, we have changed the current SDK version of our project and learned how we can view, upgrade, or downgrade the SDK. It's very easy to control the SDK version in .NET Core. Feel free to leave feedback/comment/questions related to this article in the comments section. 

Software development kit .NET

Opinions expressed by DZone contributors are their own.

Related

  • Zero to AI Hero, Part 2: Understanding Plugins in Semantic Kernel, A Deep Dive With Examples
  • Beyond n8n for Workflow Automation: Agent Graphs as Your Universal Agent Harness
  • Implementing Effective Document Fraud Detection in C#
  • How To Build A White-label AI Chatbot: Here's the Complete Process

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook