Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
351 changes: 189 additions & 162 deletions .ghal.rules.json

Large diffs are not rendered by default.

19,696 changes: 6,655 additions & 13,041 deletions .openpublishing.redirection.json

Large diffs are not rendered by default.

8 changes: 7 additions & 1 deletion docs/core/diagnostics/dotnet-trace.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,13 @@ dotnet-trace collect [--buffersize <size>] [--clreventlevel <clreventlevel>] [--

- **`--profile <profile-name>`**

A named pre-defined set of provider configurations that allows common tracing scenarios to be specified succinctly.
A named pre-defined set of provider configurations that allows common tracing scenarios to be specified succinctly. The following profiles are available:

| Profile | Description |
|---------|-------------|
|`cpu-sampling`|Useful for tracking CPU usage and general .NET runtime information. This is the default option if no profile or providers are specified.|
|`gc-verbose`|Tracks GC collections and samples object allocations.|
|`gc-collect`|Tracks GC collections only at very low overhead.|

- **`--providers <list-of-comma-separated-providers>`**

Expand Down
70 changes: 43 additions & 27 deletions docs/core/install/windows.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,22 +27,26 @@ The following table is a list of currently supported .NET releases and the versi

Windows 10 versions end-of-service dates are segmented by edition. Only **Home**, **Pro**, **Pro Education**, and **Pro for Workstations** editions are considered in the following table. Check the [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) for specific details.

- A ✔️ indicates that the version of Windows or .NET Core is still supported.
- A ❌ indicates that the version of Windows or .NET Core isn't supported on that Windows release.
- When both a version of Windows and a version of .NET Core have ✔️, that OS and .NET combination is supported.

| Operating System | .NET Core 2.1 | .NET Core 3.1 | .NET 5 |
|-----------------------------|---------------|---------------|----------------|
| ✔️ Windows 10, Version 2004 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ✔️ Windows 10, Version 1909 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ✔️ Windows 10, Version 1903 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ✔️ Windows 10, Version 1809 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ❌ Windows 10, Version 1803 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ❌ Windows 10, Version 1709 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ❌ Windows 10, Version 1703 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 |
| ❌ Windows 10, Version 1607 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 |
| ❌ Windows 10, Version 1511 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 |
| ❌ Windows 10, Version 1507 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 |
> [!TIP]
> A `+` symbol represents the minimum version.

| Operating System | .NET Core 2.1 | .NET Core 3.1 | .NET 5 |
|-----------------------------|---------------|---------------|--------|
| Windows 10, Version 2004 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1909 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1903 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1809 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1803 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1709 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1607 | ✔️ | ✔️ | ✔️ |
| Windows 8.1 | ✔️ | ✔️ | ✔️ |
| Windows 7 SP1 [ESU][esu] | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1607 | ✔️ | ✔️ | ✔️ |
| Windows 10, Version 1607 | ✔️ | ✔️ | ✔️ |
| Windows Server 2012 R2 | ✔️ | ✔️ | ✔️ |
| Windows Server Core 2012 R2 | ✔️ | ✔️ | ✔️ |
| Nano Server, Version 1809+ | ✔️ | ✔️ | ✔️ |
| Nano Server, Version 1803 | ✔️ | ✔️ | ❌ |

## Unsupported releases

Expand Down Expand Up @@ -106,15 +110,15 @@ The following Windows versions are supported with .NET Core 3.1:
| OS | Version | Architectures |
| ----------------------------- | ------------------------------ | --------------- |
| Windows Client | 7 SP1+, 8.1 | x64, x86 |
| Windows 10 Client | Version 1609+ | x64, x86 |
| Windows 10 Client | Version 1607+ | x64, x86 |
| Windows Server | 2012 R2+ | x64, x86 |
| Nano Server | Version 1803+ | x64, ARM32 |

For more information about .NET Core 3.1 supported operating systems, distributions, and lifecycle policy, see [.NET Core 3.1 Supported OS Versions](https://github.com/dotnet/core/blob/master/release-notes/3.1/3.1-supported-os.md).

# [.NET Core 3.0](#tab/netcore30)

*.NET Core 3.0 is currently out of support. For more information, see the [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).*
*.NET Core 3.0 is currently out of support. For more information, see the [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).*

The following Windows versions are supported with .NET Core 3.0:

Expand All @@ -132,7 +136,7 @@ For more information about .NET Core 3.0 supported operating systems, distributi

# [.NET Core 2.2](#tab/netcore22)

*.NET Core 2.2 is currently out of support. For more information, see the [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).*
*.NET Core 2.2 is currently out of support. For more information, see the [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).*

The following Windows versions are supported with .NET Core 2.2:

Expand Down Expand Up @@ -172,11 +176,11 @@ For more information about .NET Core 2.1 supported operating systems, distributi

Additional dependencies are required if you're installing the .NET SDK or runtime on the following Windows versions:

- Windows 7 SP1
- Windows Vista SP 2
- ✔️ Windows 8.1
- ✔️ Windows Server 2008 R2
- ✔️ Windows Server 2012 R2
- Windows 7 SP1 [ESU][esu]
- Windows Vista SP 2
- Windows 8.1
- Windows Server 2008 R2
- Windows Server 2012 R2

Install the following:

Expand Down Expand Up @@ -255,15 +259,25 @@ While Visual Studio Code doesn't come with an automated .NET Core installer like
01. [Download and install the .NET Core SDK](https://dotnet.microsoft.com/download/dotnet-core).
01. [Install the C# extension from the Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp).

## Windows Installer

The [download page](https://dotnet.microsoft.com/download/dotnet-core) for .NET provides Windows Installer executables.

When you use the MSI files to install .NET< you can customize the installation path by setting the `DOTNETHOME_X64` and `DOTNETHOME_X86` parameters:

```console
dotnet-sdk-3.1.301-win-x64.exe DOTNETHOME_X64="F:\dotnet\x64" DOTNETHOME_X86="F:\dotnet\x86"
```

## Download and manually install

As an alternative to the Windows installers for .NET, you can download and manually install the SDK or runtime. Manual install is usually performed as part of continuous integration testing. For a developer or user, it's generally better to use an [installer](https://dotnet.microsoft.com/download/dotnet-core).

Both .NET SDK and .NET Runtime can be manually installed after they've been downloaded. If you install .NET SDK, you don't need to install the corresponding runtime. First, download a binary release for either the SDK or the runtime from one of the following sites:

- ✔️ [.NET 5.0 downloads](https://dotnet.microsoft.com/download/dotnet/5.0)
- ✔️ [.NET Core 3.1 downloads](https://dotnet.microsoft.com/download/dotnet-core/3.1)
- ✔️ [.NET Core 2.1 downloads](https://dotnet.microsoft.com/download/dotnet-core/2.1)
- [.NET 5.0 downloads](https://dotnet.microsoft.com/download/dotnet/5.0)
- [.NET Core 3.1 downloads](https://dotnet.microsoft.com/download/dotnet-core/3.1)
- [.NET Core 2.1 downloads](https://dotnet.microsoft.com/download/dotnet-core/2.1)
- [All .NET Core downloads](https://dotnet.microsoft.com/download/dotnet-core)

Create a directory to extract .NET to, for example `%USERPROFILE%\dotnet`. Then, extract the downloaded zip file into that directory.
Expand Down Expand Up @@ -296,3 +310,5 @@ For more information about using .NET in a Docker container, see [Introduction t
- [Tutorial: Hello World tutorial](../tutorials/with-visual-studio.md).
- [Tutorial: Create a new app with Visual Studio Code](../tutorials/with-visual-studio-code.md).
- [Tutorial: Containerize a .NET Core app](../docker/build-container.md).

[esu]: /troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq
5 changes: 5 additions & 0 deletions docs/fsharp/tools/fsharp-interactive/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,9 @@ F# scripting is natively supported in [Visual Studio](../../get-started/get-star

## Referencing packages in F# Interactive

> [!NOTE]
> Package management system is extensible, read more [about other extensions](https://github.com/dotnet/fsharp/tree/main/src/fsharp/Microsoft.DotNet.DependencyManager).

F# Interactive supports referencing NuGet packages with the `#r "nuget:"` syntax and an optional version:

```fsharp
Expand Down Expand Up @@ -128,6 +131,8 @@ You can specify as many package references as you like in a script.
> [!NOTE]
> There's currently a limitation for scripts that use framework references (e.g.`Microsoft.NET.Sdk.Web` or `Microsoft.NET.Sdk.WindowsDesktop`). Packages like Saturn, Giraffe, WinForms are not available. This is being tracked in issue [#9417](https://github.com/dotnet/fsharp/issues/9417).

Read more about [package management extensibility and other extensions](https://github.com/dotnet/fsharp/tree/main/src/fsharp/Microsoft.DotNet.DependencyManager).

## Referencing assemblies on disk with F# interactive

Alternatively, if you have an assembly on disk and wish to reference that in a script, you can use the `#r` syntax to specify an assembly. Consider the following code in a project compiled into `MyAssembly.dll`:
Expand Down
Loading