Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Getting started with .NET 9.0 on RHEL 8
Installing and running .NET 9.0 on RHEL 8
Abstract
Providing feedback on Red Hat documentation
We appreciate your feedback on our documentation. Let us know how we can improve it.
Submitting feedback through Jira (account required)
- Log in to the Jira website.
- Click Create in the top navigation bar
- Enter a descriptive title in the Summary field.
- Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation.
- Click Create at the bottom of the dialogue.
Chapter 1. Introducing .NET 9.0
.NET is a general-purpose development platform featuring automatic memory management and modern programming languages. Using .NET, you can build high-quality applications efficiently. .NET is available on Red Hat Enterprise Linux (RHEL) and OpenShift Container Platform through certified containers.
.NET offers the following features:
- The ability to follow a microservices-based approach, where some components are built with .NET and others with Java, but all can run on a common, supported platform on RHEL and OpenShift Container Platform.
- The capacity to more easily develop new .NET workloads on Microsoft Windows. You can deploy and run your applications on either RHEL or Windows Server.
- A heterogeneous data center, where the underlying infrastructure is capable of running .NET applications without having to rely solely on Windows Server.
Chapter 2. Installing .NET 9.0
.NET 9.0 is included in the AppStream repositories for RHEL 8. The AppStream repositories are enabled by default on RHEL 8 systems.
You can install the .NET 9.0 runtime with the latest 9.0 Software Development Kit (SDK). When a newer SDK becomes available for .NET 9.0, you can install it by running sudo dnf install.
Prerequisites
Installed and registered RHEL 8.10 with attached subscriptions.
For more information, see Interactively installing RHEL from installation media.
Procedure
Install .NET 9.0 and all of its dependencies:
sudo dnf install dotnet-sdk-9.0 -y
$ sudo dnf install dotnet-sdk-9.0 -yCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Verify the installation:
dotnet --info
$ dotnet --infoCopy to Clipboard Copied! Toggle word wrap Toggle overflow The output returns the relevant information about the .NET installation and the environment.
Chapter 3. Creating an application using .NET 9.0
Learn how to create a C# "Hello World" application.
Procedure
Create a new Console application in a directory called
my-app:dotnet new console --output my-app
$ dotnet new console --output my-appCopy to Clipboard Copied! Toggle word wrap Toggle overflow Run the project:
dotnet run --project my-app
$ dotnet run --project my-appCopy to Clipboard Copied! Toggle word wrap Toggle overflow The output returns:
Hello World!
Hello World!Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 4. Publishing applications with .NET 9.0
.NET 9.0 applications can be published to use a shared system-wide version of .NET or to include .NET.
The following methods exist for publishing .NET 9.0 applications:
- Self-contained deployment (SCD) - The application includes .NET. This method uses a runtime built by Microsoft.
- Framework-dependent deployment (FDD) - The application uses a shared system-wide version of .NET.
When publishing an application for RHEL, Red Hat recommends using FDD, because it ensures that the application is using an up-to-date version of .NET, built by Red Hat, that uses a set of native dependencies.
Prerequisites
Existing .NET application.
For more information about how to create a .NET application, see Creating an application using .NET.
4.1. Publishing .NET applications
The following procedure outlines how to publish a framework-dependent application.
Procedure
Publish the framework-dependent application:
dotnet publish my-app -f net9.0
$ dotnet publish my-app -f net9.0Copy to Clipboard Copied! Toggle word wrap Toggle overflow Replace my-app with the name of the application you want to publish.
Optional: If the application is for RHEL only, trim out the dependencies needed for other platforms:
dotnet publish my-app -f net9.0 -r rhel.8-architecture --self-contained false
$ dotnet publish my-app -f net9.0 -r rhel.8-architecture --self-contained falseCopy to Clipboard Copied! Toggle word wrap Toggle overflow Replace architecture based on the platform you are using:
-
For Intel:
x64 -
For IBM Z and LinuxONE:
s390x -
For 64-bit Arm:
arm64 -
For IBM Power:
ppc64le
-
For Intel:
Chapter 5. Running .NET 9.0 applications in containers
Use the ubi8/dotnet-90-runtime image to run a .NET application inside a Linux container.
The following example uses Podman.
Procedure
Create a new MVC project in a directory called
mvc_runtime_example:dotnet new mvc --output mvc_runtime_example
$ dotnet new mvc --output mvc_runtime_exampleCopy to Clipboard Copied! Toggle word wrap Toggle overflow Publish the project:
dotnet publish mvc_runtime_example -f net9.0 /p:PublishProfile=DefaultContainer /p:ContainerBaseImage=registry.access.redhat.com/ubi8/dotnet-90-runtime:latest
$ dotnet publish mvc_runtime_example -f net9.0 /p:PublishProfile=DefaultContainer /p:ContainerBaseImage=registry.access.redhat.com/ubi8/dotnet-90-runtime:latestCopy to Clipboard Copied! Toggle word wrap Toggle overflow Run your image:
podman run -rm -p8080:8080 mvc_runtime_example
$ podman run -rm -p8080:8080 mvc_runtime_exampleCopy to Clipboard Copied! Toggle word wrap Toggle overflow View the application running in the container:
xdg-open http://127.0.0.1:8080
$ xdg-open http://127.0.0.1:8080Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 6. Migration from previous versions of .NET
6.1. Migration from previous versions of .NET
Microsoft provides instructions for migrating from most previous versions of .NET Core.
If you are using a version of .NET that is no longer supported or want to migrate to a newer .NET version to expand functionality, see the following articles:
- Migrate from ASP.NET Core 8.0 to 9.0
- Migrate from ASP.NET Core 7.0 to 8.0
- Migrate from ASP.NET Core 6.0 to 7.0
- Migrate from ASP.NET Core 5.0 to 6.0
- Migrate from ASP.NET Core 3.1 to 5.0
- Migrate from ASP.NET Core 3.0 to 3.1
- Migrate from ASP.NET Core 2.2 to 3.0
- Migrate from ASP.NET Core 2.1 to 2.2
- Migrate from .NET Core 2.0 to 2.1
- Migrate from ASP.NET to ASP.NET Core
- Migrating .NET Core projects from project.json
- Migrate from project.json to .csproj format
If migrating from .NET Core 1.x to 2.0, see the first few related sections in Migrate from ASP.NET Core 1.x to 2.0. These sections provide guidance that is appropriate for a .NET Core 1.x to 2.0 migration path.
6.2. Porting from .NET Framework
Refer to the following Microsoft articles when migrating from .NET Framework:
- For general guidelines, see Porting to .NET Core from .NET Framework.
- For porting libraries, see Porting to .NET Core - Libraries.
- For migrating to ASP.NET Core, see Migrating to ASP.NET Core.
Several technologies and APIs present in the .NET Framework are not available in .NET Core and .NET. If your application or library requires these APIs, consider finding alternatives or continue using the .NET Framework. .NET Core and .NET do not support the following technologies and APIs:
- Desktop applications, for example, Windows Forms and Windows Presentation Foundation (WPF)
- Windows Communication Foundation (WCF) servers (WCF clients are supported)
- .NET remoting
Additionally, several .NET APIs can only be used in Microsoft Windows environments. The following list shows examples of these Windows-specific APIs:
-
Microsoft.Win32.Registry -
System.AppDomains -
System.Security.Principal.Windows
Several APIs that are not supported in the default version of .NET may be available from the Microsoft.Windows.Compatibility NuGet package. Be careful when using this NuGet package. Some of the APIs provided (such as Microsoft.Win32.Registry) only work on Windows, making your application incompatible with Red Hat Enterprise Linux.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}