Experience error-free AI audio transcription that's faster and cheaper than human transcription and includes speaker recognition by default! (Get started for free)
Do I need to consider server-side rendering if I'm building a self-contained app?
According to Microsoft Learn, when you publish your app as self-contained, it includes the .NET runtime and libraries, and users can run it on a machine that doesn't have .NET installed.
Building a self-contained app means the app includes the .NET runtime and libraries, making it possible to run on a machine without .NET installed.
Self-contained apps are useful for deploying desktop applications or creating standalone executables that don't require the .NET runtime to be installed separately.
Publishing an app as self-contained can result in a larger executable size, which may not be necessary for all types of applications.
Some developers may need to consider other factors, such as the target platform and architecture, when deciding whether to publish their app as self-contained.
You don't necessarily need to have .NET Core installed on a system to use self-contained apps, but your app relies on .NET Core being present on the target machine.
To create a self-contained application, you can run the command "dotnet publish -c Release -r ubuntu1404x64" to include the .NET runtime and libraries.
A self-contained application includes all the components it needs, including the .NET runtime, making it possible to run on a machine without .NET installed.
Self-contained apps are a great option for deploying .NET applications, including NET Core.
You can reduce the total size of compatible self-contained apps by publishing them with trimming enabled in NET 6 and later versions.
Trimming removes parts of the framework and referenced assemblies that are not on any code path or potentially referenced in runtime reflection, enabling smaller executable sizes.
In NET 6 and later versions, you can use the NET CLI to publish apps with trimming, reducing the total size of compatible self-contained apps.
Self-contained executables can be built for Windows, Linux, and macOS platforms using the NET Core 3.0 SDK.
Building an application as a single file or self-contained executable on NET Core 3.0 involves using trimming to remove unused code from the self-contained executable.
Framework-dependent and self-contained deployments have different requirements, and choosing the right deployment mode depends on the project's needs and target environments.
.NET Core 3.0 provides strong naming and strong signing for self-contained deployments.
In NET Core 3.0, you can use the `PublishReadyToRun` feature to publish your app as a self-contained executable that includes the .NET runtime and libraries.
Self-contained deployments are useful for deployment scenarios where the target machine has .NET Core already installed.
Framework-dependent deployments are useful when the target machine has the correct version of .NET Framework installed.
When deciding whether to publish your app as self-contained, consider factors such as the target platform, architecture, and runtime dependencies.
Experience error-free AI audio transcription that's faster and cheaper than human transcription and includes speaker recognition by default! (Get started for free)