


.NET Core CLI tool documentation dotnet-install script reference
Name
dotnet-install.ps1 | dotnet-install.sh - Script and shared runtime for installing command line interface (CLI) tools
Summary
Windows:
dotnet-install.ps1 [-Channel] [-Version] [-InstallDir] [-Debug] [-NoPath] [-SharedRuntime]
OS X/Linux:
dotnet-install.sh [--channel] [--version] [--install-dir ] [--debug] [--no-path] [--shared-runtime]
Description
The dotnet-install installation script is used to execute non-administrator installation of the CLI toolchain and shared runtime. You can download the script from our CLI GitHub repo.
It is mainly used to help automation scenarios and non-administrator installations. There are two scripts, one is PowerShell that works on Windows and another bash script that works on Linux/OS X. Both of them have the same behavior. Bash scripts also "understand" PowerShell switches, so you can use them across the board.
The installation script will be generated by downloading the ZIP/tarball (compressed package) file from the CLI, and will be installed in the default location or in the location specified by --install-dir. By default, the installation script will download the SDK and install it; if you just want to get the shared runtime, you can specify the --shared-runtime parameter.
By default, the installation script adds the installation location to the $PATH of the current session. This can be overridden if the --no-path parameter is used.
Please install all required dependencies before running the script.
You can use the --version parameter to install a specific version. The specified version requires a 3-part version (for example: 1.0.0-13232). If omitted, it will default to the first global.json file containing an sdkVersion node found in the called script's parent folder. If it doesn't exist, it will use the latest one.
You can also use this script to get debug binaries of SDK or shared runtime debugging symbols by using the --debug parameter. If you don't do this the first time you install it, and later on you actually do need the debugging symbols, you can rerun the script with this parameter and the version you installed.
Options
Options for different script implementations.
PowerShell (Windows)
-Channel [CHANNEL]
The channel to install (for example: "future", "preview", "production"). The default version is "Production".
-Version [VERSION]
The installed CLI version. You need to specify the 3-part version (for example: 1.0.0-13232). If omitted, it will default to the first global.json file containing an sdkVersion node found in the called script's parent folder. If it doesn't exist, it will use the latest one.
-InstallDir [DIR]
The installation path. Create the directory if it does not exist. The default value is %LocalAppData%.dotnet.
-Debug
true indicates that a larger package containing debugging symbols should be used; otherwise, false. The default value is false.
-NoPath
true indicates that the prefix/installation directory is not exported to the path of the current session; otherwise, false. The default value is false, that is, PATH is modified. This makes the CLI tool available immediately after installation.
-SharedRuntime
true only installs the shared runtime. false installs the entire SDK. The default value is false.
Bash (OS The default version is "Production".
--version [VERSION]
The installed CLI version. You need to specify the 3-part version (for example: 1.0.0-13232). If omitted, it will default to the first global.json file containing an sdkVersion node. If it doesn't exist, it will use the latest one.
--install-dir [DIR]
The installation path. Create the directory if it does not exist. The default value is %HOME%/.dotnet.
--debug
true indicates that a larger package containing debugging symbols should be used; otherwise, false . The default value is false.
--no-path
true indicates that the prefix/installation directory is not exported to the path of the current session; otherwise, false. The default value is false, that is, PATH is modified. This makes the CLI tool available immediately after installation.
--shared-runtime
true only installs the shared runtime. false installs the entire SDK. The default value is false.
Example
Windows:
./dotnet-install.ps1 -Channel Future
OS X/Linux:
./dotnet-install.sh --channel Future
Windows:
./dotnet-install.ps1 -Channel preview -InstallDir C:cli
OS X/Linux:./dotnet-install.sh --channel preview --install-dir ~ /cli
Install the latest preview version to the specified location.
Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Whether you are a beginner or an experienced professional, mastering C# will pave the way for your career.

The development of artificial intelligence (AI) technologies is in full swing today, and they have shown great potential and influence in various fields. Today Dayao will share with you 4 .NET open source AI model LLM related project frameworks, hoping to provide you with some reference. https://github.com/YSGStudyHards/DotNetGuide/blob/main/docs/DotNet/DotNetProjectPicks.mdSemanticKernelSemanticKernel is an open source software development kit (SDK) designed to integrate large language models (LLM) such as OpenAI, Azure

If you are a .NET developer, you must be aware of the importance of optimizing functionality and performance in delivering high-quality software. By making expert use of the provided resources and reducing website load times, you not only create a pleasant experience for your users but also reduce infrastructure costs.

In terms of high-concurrency request processing, .NETASP.NETCoreWebAPI performs better than JavaSpringMVC. The reasons include: AOT early compilation, which reduces startup time; more refined memory management, where developers are responsible for allocating and releasing object memory.

C#.NET interview questions and answers include basic knowledge, core concepts, and advanced usage. 1) Basic knowledge: C# is an object-oriented language developed by Microsoft and is mainly used in the .NET framework. 2) Core concepts: Delegation and events allow dynamic binding methods, and LINQ provides powerful query functions. 3) Advanced usage: Asynchronous programming improves responsiveness, and expression trees are used for dynamic code construction.

Interview with C# senior developer requires mastering core knowledge such as asynchronous programming, LINQ, and internal working principles of .NET frameworks. 1. Asynchronous programming simplifies operations through async and await to improve application responsiveness. 2.LINQ operates data in SQL style and pay attention to performance. 3. The CLR of the NET framework manages memory, and garbage collection needs to be used with caution.

C# is a modern, object-oriented programming language developed by Microsoft and as part of the .NET framework. 1.C# supports object-oriented programming (OOP), including encapsulation, inheritance and polymorphism. 2. Asynchronous programming in C# is implemented through async and await keywords to improve application responsiveness. 3. Use LINQ to process data collections concisely. 4. Common errors include null reference exceptions and index out-of-range exceptions. Debugging skills include using a debugger and exception handling. 5. Performance optimization includes using StringBuilder and avoiding unnecessary packing and unboxing.

C#.NETisversatileforbothwebanddesktopdevelopment.1)Forweb,useASP.NETfordynamicapplications.2)Fordesktop,employWindowsFormsorWPFforrichinterfaces.3)UseXamarinforcross-platformdevelopment,enablingcodesharingacrossWindows,macOS,Linux,andmobiledevices.
