.NET On CentOS.

Home » CentOS » .NET On CentOS.
CentOS 7 Comments

Hi there, I was reading about it. https://www.redhat.com/en/about/blog/net-core-now-available-and-supported-red-hat-enterprise-linux-and-red-hat-openshift

What will happen with CentOS and .NET?
In the side of security and stability.

7 thoughts on - .NET On CentOS.

  • –FwdLdLIftDCWIBm2SrAi3aTokvFgnLVIv Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    That announcement, and this website:


    Are both Microsoft and Red Hat initiatives / agreements. The .NET being discussed is in OpenShift containers running on Microsoft’s Azure Cloud.

    None of that is currently slated, to the best of my knowledge, to be rolled into the Base distribution for RHEL. Therefore it is also not being added into the CentOS Linux distribution. If / when Red Hat does add things into the base RHEL Server, Workstation, Desktop platforms and releases the source code for it, we will of course rebuild that source code and add the resulting software to CentOS Linux.

    Another method of getting things into the CentOS universe is to start a Special Interest Group that provides optional software to CentOS
    repositories (Currently things like Xen support, GlusterFS, Ceph, RDO, Software Collections, Opennfv, etc). I do not know of any current or planned .NET SIG for CentOS. There certainly could be one in the future
    (if there is interest), or one of the current SIGs might need to bring in .NET for developing software for their SIG. But I currently know of no one bringing it in.

    Microsoft has stated that will also make .NET Core available for Ubuntu, Debian and CentOS Linux. That is not something that I know anything about right now either.

    The CentOS team certainly welcomes development software like .NET being provided by the software owner for use on CentOS Linux.

    Thanks, Johnny Hughes


  • I’d expect it to show up in SCL at some point:


    Until then, the CentOS build instructions on Microsoft’s official download page work just fine, at least on EL7:


    RC3 apparently just shipped, which has caused some version incompatibilities in the .NET package repositories. I was able to get the default C# “hello, world” project to build and run:

    $ mkdir test
    $ cd test
    $ dotnet new –lang c#
    $ dotnet restore
    $ dotnet build
    $ dotnet run
    Hello World!

    …but the F# project (–lang f#) chokes due to a version incompatibility. This should shake out soon.

    Beware that .NET Core is not the same thing as .NET. It is very much stripped down compared to the Windows .NET platform. It is mainly intended for headless server-side applications, like serving ASP.NET sites.

    I’m guessing you’re asking if .NET Core will be secure. I assume it will be as secure as any VM type interpreter, such as Java or Flash. That is to say, theoretically quite secure, but in practice only as secure the platform’s maintainers put in the effort to make it secure. My advice: wrap it in SELinux, VMs, chroots, etc., just as you would any other executable code you want walled off from the rest of your infrastructure.

    As for stability, it’s still pre-1.0. Don’t bet your business on it today. If you need a stable .NET implementation for Linux today, use Mono.

  • I’ve since learned that the problem is already fixed in the code, it is just working its way out to a released version at the moment.

    Since my previous post, I stumbled across this well-written “what it is/is not” type of document from the core project:


    Well worth a read if you are at all curious about why you’d care about .NET on CentOS, or why we need a second implementation.

    …on CentOS, I mean. I’ve just seen the news that 1.0.0 final binaries are shipping on other platforms.

    But by that very token, why are you asking about stability and security so early? 1.0.0 of *anything* is rarely rock-solid, and you can’t say the first version of *anything* is secure until it’s been proven over time to be so.

    Give it time.

  • This is business, I think it is much better to widen the audience or supported platform. I think same with what they did with Office Open XML, which is good and beneficial to all.

  • –K2SKMDMh43oggPOKW8H9QOeksdA6lggLa Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    I am hearing now that there should be some kind of release of dotnet source code into git.CentOS.org sometime soon. I don’t yet know if it will be code that goes into base CentOS or if it will be code built buy one or more of the Special Interest Groups.

    When I know more, so will the list.

    Thanks, Johnny Hughes


  • Hi,

    Great question!

    On the CentOS side, we are working with both the upstreams ( RedHat and Microsoft in this case ) to make sure we get deliver the content, in the various formats, easily and everywhere. And I’m keen to make sure we are able to do this in a way that the upstream developers of the code know and understand the delivery mechanics for this. This including actually looking at onboarding the dotnet-core on Linux team into a SIG and then setting up build, test, release, lifecycle loops from the CentOS Project infra directly.

    On the downstream product side, once the content is available we will work through the build machanics and take it from there.