- .NET Core - Environment Setup
Looking for:
Download Visual Studio Tools - Install Free for Windows, Mac, Linux. |
.NET SDKs downloads for Visual Studio.
If you're building an end user tool or application, a self-contained application that has everything it needs included is usually a better call. But if you're building developer tools, the lightweight and universal.
NET Core Tool distribution experience is often preferable. The advantage of building a. NET Core Tool is that it's not platform-specific. Like a NuGet component, a. NET assemblies. There's no launching executable packaged. If dotnet tool can run on the computer, so can your. NET Core Tool. This means that you can build a single, relatively small NuGet package as a. NET Core Tool and it will work on all supported. NET Core platforms, assuming your code is written to otherwise use platform-agnostic features.
That's cool: The. NET Core Tool provides you with cross-platform functionality without having to build and maintain multiple platform-specific loaders and it keeps the deployment size very small. Let's create a very simple project called MagicWindBall that predicts wind conditions for the day.
It's a play on the words of Magic Eightball, which is a fake fortune telling device and I'm hijacking the idea to tell me my wind fortunes. Start by creating a. NET Core Console project. I'll use the dotnet command line tooling, but you can also use Visual Studio or Rider, etc. From the command line, start by creating a new folder with the Project name, and then create a project in that folder:.
This creates a new project MagicWindBall. I'll use VS Code here, as shown in Figure 1 , which makes it easy to open the projects from a folder via the code. This project is very simple, with an imaginary wind forecast generator that randomly displays a string from a list of pre-defined wind condition strings.
First, let's make sure the code works as a regular Console application. Open a Terminal in the project folder and do:. NET Core Tools use the existing. NET tool infrastructure for creation, publishing, and installing tools. You now have a plain. NET Core Console application. To turn this into a. NET Core Tool, add a few specific settings to the project file.
At minimum, you need to add a few. NET Core Tool-specific settings to the project. With these flags in place, you can now build the project and generate the.
This builds the project and creates a NuGet Package in the. You can use the NuGet Package Explorer to spy into the package to see what's in the package, as shown in Figure 2.
Once you've created the NuGet Package, you'll probably want to test it locally first before publishing it. You can do that by installing the.
NET Core Tool locally from a folder. To install, you use dotnet tool install or dotnet tool update. You can test the package locally by installing the NuGet component from a folder by specifying the --add-source. Et voila! You've just installed the. NET Core Tool locally and you can now run the tool simply by typing magicwindball into the Terminal from on your computer. Figure 3 shows building, installing, and running the tool in a Terminal window. NET Component. Note that NuGet Package signing is optional, but because I already have a publisher certificate, I'm using it to sign my package.
For the nuget push to work, you'll need to set the active NuGet publishing ID before you publish the package. Figure 4 shows what the published package looks like on the NuGet Package Store site. Once published, the package becomes accessible within a few minutes. Feed listings can take a bit longer, so you may have to explicitly specify a version on the command line using the --version flag. You can now install and run the component from the NuGet Package Store. Figure 5 shows the install and run sequence.
If you need to update the. NET Core Tool, make your code changes and increment the version number of the project then simply re-publish to NuGet. A new package with the new version number is created and pushed, which then becomes available on NuGet.
You can then use dotnet tool update -g dotnet-magicwindball to update the local tool installation to the updated version. NET Core Tools are deployed as. Rather, when a tool is installed, a platform-specific, native launcher executable is generated that acts as a proxy launcher for the. NET Core runtime, which then bootstraps the. Figure 1 Visual Studio. NET Core folders. Obviously, each project type generates a different set of files, as shown in Figure 2.
NET Framework 1. This is the standard AssemblyInfo. NET projects since. NET was first released in NET Core project. It identifies such things as project references, build options like the version number, and identifies the platform to compile to—whether.
NET Core or. NET Framework, for example. More on this shortly. It includes specific package version numbers, unlike the project. Without project. NET 7 Preview. Want to try out the latest preview? NET 7. NET Core. Supported versions Download matrix for. The software development kit SDK includes everything you need to build and run. NET applications, using command-line tools and any editor like Visual Studio.
Runtime Windows Tooltip: Do you want to run apps? The runtime includes everything you need to run. NET applications. You can see the syntax below to specify the set of targets that you want to build for, as a semicolon-separated list. This will also automatically set the right defines that you can use in your code to enable or disable specific blocks of code depending on the target frameworks. You will be able to migrate existing project.
The following project. There are a set of useful commands exposed by the. These commands will continue to be included with the. The only difference is that the. The primary role for the. In the meanwhile you can safely continue to use the existing project. We think this is a big step forward for a unified. NET platform that will make your life easier by bringing your new and existing code to any application type and platform.
And because we develop in the open, you are welcome to join the GitHub repos where this work is taking place:. Comments are closed. NET Meetup Events. Web apps with ASP. Mobile apps with Xamarin. Microservices with Docker Containers.
Modernizing existing. If you are aiming to run. NET Core application, then install. NET Core Runtime on your server or cloud or client desktop. Click on the Download. It will download. After installation, you can now develop. Let's learn about it next. C ASP.
Comments
Post a Comment