Microsoft’s decision to make .NET Core open source means it’s time for Linux developers to get comfortable and start experimenting.
If they use Linux, you get a list of open source projects: Go, Python, Ruby, Rails, Grails, Node.js, Haskell, Elixir, etc. It seems that as each new language—Kotlin, anyone?—is introduced, Linux picks up a new set of developers.
So leave it to Microsoft (Microsoft?!?) to throw a wrench into this theory by making the .NET framework, coined .NET Core, open source and available to run on any platform. Windows, Linux, MacOS, and even a television OS: Samsung’s Tizen. Add in Microsoft’s other .NET flavors, including Xamarin, and you can add the iOS and Android operating systems to the list. (Seriously? I can write a Visual Basic app to run on my TV? What strangeness is this?)
Given this situation, it’s about time Linux developers get comfortable with .NET Core and start experimenting, perhaps even building production applications. Pretty soon you’ll meet that person: “I use Linux … I write C# apps.” Brace yourself: .NET is coming.
How to install .NET Core on Linux
The list of Linux distributions on which you can run .NET Core includes Red Hat Enterprise Linux (RHEL), Ubuntu, Debian, Fedora, CentOS, Oracle, and SUSE.
Each distribution has its own installation instructions. For example, consider Fedora 26:
Step 1: Add the dotnet product
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc sudo sh -c 'echo -e "[packages-microsoft-com-prod]\nname=packages-microsoft-com-prod \nbaseurl=https://packages.microsoft.com/yumrepos/microsoft-rhel7.3-prod\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" > /etc/yum.repos.d/dotnetdev.repo'
Step 2: Install the .NET Core SDK.
sudo dnf update sudo dnf install libunwind libicu compat-openssl10 sudo dnf install dotnet-sdk-2.0.0
Creating the Hello World console app
Now that you have .NET Core installed, you can create the ubiquitous “Hello World” console application before learning more about .NET Core. After all, you’re a developer: You want to create and run some code now. Fair enough; this is easy. Create a directory, move into it, create the code, and run it:
mkdir helloworld && cd helloworld dotnet new console dotnet run
You’ll see the following output:
$ dotnet run Hello World!
What just happened?
Let’s take what just happened and break it down. We know what the mkdir and cd did, but after that?
dotnew new console
As you no doubt have guessed, this created the “Hello World!” console app. The key things to note are: The project name matches the directory name (i.e., “helloworld”); the code was build using a template (console application); and the project’s dependencies were automatically retrieved by the dotnet restore command, which pulls from nuget.org.
If you view the directory, you’ll see these files were created:
Program.cs is the C# console app code. Go ahead and take a look inside (you already did … I know … because you’re a developer), and you’ll see what’s going on. It’s all very simple.
Helloworld.csproj is the MSBuild-compatible project file. In this case there’s not much to it. When you create a web service or website, the project file will take on a new level of significance.
This command did two things: It built the code, and it ran the newly built code. Whenever you invoke dotnet run, it will check to see if the *.csproj file has been altered and will run the dotnet restore command. It will also check to see if any source code has been altered and will, behind the scenes, run the dotnet buildcommand which—you guessed it—builds the executable. Finally, it will run the executable.
Where is my executable?
Oh, it’s right there. Just run which dotnet and you’ll see (on RHEL):
That’s your executable.
When you create a dotnet application, you’re creating an assembly … a library … yes, you’re creating a DLL. If you want to see what is created by the dotnet build command, take a peek at bin/Debug/netcoreapp2.0/. You’ll see helloworld.dll, some JSON configuration files, and a helloworld.pdb (debug database) file. You can look at the JSON files to get some idea as to what they do (you already did … I know … because you’re a developer).
When you run dotnet run, the process that runs is dotnet. That process, in turn, invokes your DLL file and it becomes your application.
Here’s where .NET Core really starts to depart from the Windows-only .NET Framework: The DLL you just created will run on any system that has .NET Core installed, whether it be Linux, Windows, or MacOS. It’s portable. In fact, it is literally called a “portable application.”
What if you want to distribute an application and don’t want to ask the user to install .NET Core on their machine? (Asking that is sort of rude, right?) Again, .NET Core has the answer: the standalone application.
Creating a standalone application means you can distribute the application to any system and it will run, without the need to have .NET Core installed. This means a faster and easier installation. It also means you can have multiple applications running different versions of .NET Core on the same system. It also seems like it would be useful for, say, running a microservice inside a Linux container. Hmmm…
What’s the catch?
Okay, there is a catch. For now. When you create a standalone application using the dotnet publish command, your DLL is placed into the target directory along with all of the .NET bits necessary to run your DLL. That is, you may see 50 files in the directory. This is going to change soon. An already-running-in-the-lab initiative, .NET Native, will soon be introduced with a future release of .NET Core. This will build one executable with all the bits included. It’s just like when you are compiling in the Go language, where you specify the target platform and you get one executable; .NET will do that as well.
You do need to build once for each target, which only makes sense. You simply include a runtime identifier and build the code, like this example, which builds the release version for RHEL 7.x on a 64-bit processor:
dotnet publish -c Release -r rhel.7-x64
Web services, websites, and more
So much more is included with the .NET Core templates, including support for F# and Visual Basic. To get a starting list of available templates that are built into .NET Core, use the command dotnet new –help.
Hint: .NET Core templates can be created by third parties. To get an idea of some of these third-party templates, check out these templates, then let your mind start to wander…
Like most command-line utilities, contextual help is always at hand by using the –help command switch. Now that you’ve been introduced to .NET Core on Linux, the help function and a good web search engine are all you need to get rolling.
Author: Don Schenck
Source : https://opensource.com/article/17/11/net-linux
License : Attribution 4.0 International
You may be interested
How to create a Blockchain using Node.jssimoneadmin - December 22, 2018
In this article, I will talk about the basics of Blockchain. We will discuss the fundamental concepts of the blockchain.…