When you build your .NET Core project, NuGet packages are retrieved from nuget.org by default. Sometimes, however, you might want to use a local NuGet repository. For example, you may want to:
- use private NuGet packages, but you don’t want anyone except your associates to see them.
- cache a NuGet repository at a server near your build servers
- leave your build server disconnected from the Internet.
I’ll explain how to set up a private NuGet server on OpenShift and how you can use this NuGet server when building your .NET Core project in OpenShift using s2i-dotnetcore.
Continue reading “Running a NuGet server on OpenShift”
Sometimes things are really easy. This is one of those cases. There are only six steps to creating and running your first .NET program on Red Hat Enterprise Linux (RHEL).
Continue reading “Creating Your First .NET Program on Red Hat Enterprise Linux”
If you want to use secret configuration which you don’t want to store the code repository during developing ASP.NET Core app, what will you do? ASP.NET Core provides Secret Manager tool. Then how about developing on OpenShift? I’d like to talk about Secret Manager tool and working OpenShift secrets for ASP.NET Core in this blog.
Continue reading “Working with OpenShift secrets for ASP.NET Core”
This post may be short, but if you’re new to .NET Core, it’s valuable.
Continue reading Gems: A Few Helpful dotnet commands
In my first .NET core post, I set out on a journey to conquer the new world of .NET Core (formerly DNX) on Red Hat Enterprise Linux (RHEL). In my ignorance I believed I would do a short post on firing up RHEL, installing .NET Core, and then converting an application from .NET to .NET Core before adding it as a build job to a new TeamCity instance. The best laid plans seem to be the ones that get me closest to throwing my computer out the window, and Part 1 stands as a comedy of my errors. With all of that sorted, however, it is time to finish the job and start working with .NET Core on RHEL. (RHEL is now available at no cost for developer use! You can download it here.)
The Goals (A Review)
Just to go over our goals one more time…
- Create a functioning VM on my local machine with RHEL 7.2 and Windows Hyper-V
- Install Visual Studio Code
- Install .NET Core
- Convert a simple .NET project to work on .NET Core
- Install TeamCity
- Create a TeamCity Build Job for the .NET project
Continue reading “Converting a .NET application to .NET Core (formerly DNX)”
Despite spending plenty of time in Red Hat Linux while I was young, I have become an unabashed Windows environment super-user/programmer. Still, it’s hard to discount the multitude of ways that the *nix community stands ahead and alone, so when Microsoft and Red Hat announced their partnership to bring .NET to Linux, I had no choice but to take notice. As an experiment, I am going to go through setting up Red Hat Enterprise Linux (RHEL) and .NET Core to see if I can’t have a little fun and test the technology before it’s even at its first release.
This post is the first of two, with the final goal of learning how to convert an existing .NET application to .NET Core. But first we have to set up .NET Core on RHEL. (Also note that RHEL is now available at no cost for developer use! You can download it here.)
Continue reading “A Windows Guy’s Guide: Setting up .NET Core on RHEL”
Red Hat is committed to making .NET a First Class citizen on Red Hat Enterprise Linux (RHEL). To that end, we’re working furiously to make sure everything’s perfect before we make .NET available by simply running:
yum install rh-dotnetcore10
In the meantime, I can’t wait.
No, literally, I can’t wait — you don’t need to either. You can hop over to Microsoft’s .NET download site and get .NET for RHEL. (What? You didn’t get your zero-dollar developer copy of RHEL? I’ll wait while you download it…)
Continue reading “.NET on RHEL: I can’t wait, and neither should you”