Lee Coward
GitHub
commit
4fb372fb1e
|
|
@ -7,6 +7,11 @@ This is a somewhat currated list of commits across the entire .NET Core 2.1.1 de
|
|||
* [CoreFX](#corefx)
|
||||
* [WCF](#wcf)
|
||||
|
||||
## CLI
|
||||
|
||||
* [`[4050c6374]`](https://github.com/dotnet/cli/commit/4050c6374) The "pack" command under 'buildCrossTargeting' for 'Microsoft.DotNet.MSBuildSdkResolver' now throws a "NU5104" warning/error because the SDK stage0 was changed to "2.1.300" [change was intended].
|
||||
* [`[ea539c7f6]`](https://github.com/dotnet/cli/commit/ea539c7f6) Add retry when Directory.Move (#9313)
|
||||
|
||||
## CoreCLR
|
||||
|
||||
* [`[13ea3c2c8e]`](https://github.com/dotnet/coreclr/commit/13ea3c2c8e) Fix alternate stack for Alpine docker on SELinux (#17936) (#17975)
|
||||
|
|
|
|||
64
release-notes/2.1/2.1.1-known-issues.md
Normal file
64
release-notes/2.1/2.1.1-known-issues.md
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
# .NET Core 2.1.1 Known Issues
|
||||
|
||||
This document lists known issues for **.NET Core 2.1.1** which may be encountered during usage.
|
||||
|
||||
#### Offline restore is broken in .NET Core SDK 2.1.301 ([aspnet/1220](https://github.com/aspnet/Universe/issues/1220))
|
||||
|
||||
##### Workaround
|
||||
|
||||
There are 2 workarounds to resolve this situation
|
||||
|
||||
1. Perform an online restore to obtain Microsoft.NETCore.App 2.1.0 from nuget.org before attempting to work offline.
|
||||
2. Set `RuntimeFrameworkVersion` to 2.1.1. This will prevent nuget from trying to go online, and will allow the app to build and run locally but deployment to a machine that doesn’t have 2.1.1 runtime installed will fail.
|
||||
|
||||
#### Installing on SLES 12 SP3 reports `krb5-mini` dependency is missing ([core-setup/4262](https://github.com/dotnet/core-setup/issues/4262))
|
||||
|
||||
``` bash
|
||||
> sudo zypper install dotnet-sdk-2.1
|
||||
Refreshing service 'cloud_update'.
|
||||
Loading repository data...
|
||||
Reading installed packages...
|
||||
Resolving package dependencies...
|
||||
|
||||
Problem: nothing provides krb5-mini needed by dotnet-runtime-deps-2.1-2.1.1-1.x86_64
|
||||
Solution 1: do not install dotnet-sdk-2.1-2.1.301-1.x86_64
|
||||
Solution 2: break dotnet-runtime-deps-2.1-2.1.1-1.x86_64 by ignoring some of its dependencies
|
||||
|
||||
Choose from above solutions by number or cancel [1/2/c] (c):
|
||||
```
|
||||
|
||||
krb5 is generally installed by default. This can be confirmed with the following.
|
||||
|
||||
``` bash
|
||||
> zypper search krb5
|
||||
Loading repository data...
|
||||
Reading installed packages...
|
||||
|
||||
S | Name | Summary | Type
|
||||
---+-----------------+------------------------------------------------+--------
|
||||
i | krb5 | MIT Kerberos5 Implementation--Libraries | package
|
||||
i+ | krb5-client | MIT Kerberos5 implementation - client programs | package
|
||||
i | libndr-krb5pac0 | NDR marshallers for the KRB5 PAC formats | package
|
||||
```
|
||||
|
||||
If it is not installed, run `zypper install krb5-client`, then install dotnet core. When presented with the missing dependency prompt, choose 'Solution 2' to continue with the installation.
|
||||
|
||||
## Previous known issues fixed in this release
|
||||
|
||||
[[Fixed]](https://github.com/dotnet/coreclr/pull/17975) - [coreclr/17931](https://github.com/dotnet/coreclr/issues/17931) and [dotnet-docker/561](https://github.com/dotnet/dotnet-docker/issues/561)
|
||||
|
||||
Using Alpine docker image from system w/ SELinux execheap enforcement triggers segfault.
|
||||
|
||||
This issue will be fixed in the first update for 2.1.
|
||||
|
||||
[[Fixed]](https://github.com/dotnet/cli/pull/9313) - [cli/9289](https://github.com/dotnet/cli/issues/9289)
|
||||
|
||||
Using `dotnet install` or `dotnet uninstall` to manage Global Tools sometimes results in an `access denied` error. This occurs because another process, like an indexer, has not released a handle on the Global Tools files.
|
||||
|
||||
*Workaround*
|
||||
|
||||
**Global Tools created with .NET Core SDK 2.1.300 Preview 1 are not compatible with later versions.**
|
||||
|
||||
Also: Ensure that global.json does not pin to .NET Core SDK 2.1.300 Preview 1 on either for a directory where you are developing global tools or a directory from which you are installing global tools.
|
||||
|
||||
*Workaround* - Manually remove these tools.
|
||||
89
release-notes/2.1/2.1.1.md
Normal file
89
release-notes/2.1/2.1.1.md
Normal file
|
|
@ -0,0 +1,89 @@
|
|||
# .NET Core June 2018 Update - June 19, 2018
|
||||
|
||||
.NET Core 2.1.1 is available for download and usage in your environment. Have a look at the [Known Issues](2.1.0-known-issues.md) document as there are a few things to be aware of before installing. A [changelist](https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.1-commit.md) for the entire 2.1 development cycle is also available. This does not include ASP.NET Core or Entity Framework Core.
|
||||
|
||||
* [Download .NET Core](https://www.microsoft.com/net/download/dotnet-core/)
|
||||
|
||||
## Blog Round up
|
||||
|
||||
* [.NET Core](https://blogs.msdn.microsoft.com/dotnet/)
|
||||
* [ASP .NET Core](https://blogs.msdn.microsoft.com/webdev/)
|
||||
* [Entity Framework Core](https://blogs.msdn.microsoft.com/dotnet/)
|
||||
|
||||
The .NET Core SDK 2.1 includes .NET Core 2.1 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.1, running `dotnet --version` will show that you're running version `2.1.301` of the .NET Core tools.
|
||||
|
||||
`dotnet --info` has been greatly enhanced in .NET Core 2.1 and now provides detailed information on installed .NET Core components.
|
||||
|
||||
Your feedback is important and appreciated. We've created an issue at [dotnet/core #XXXX](https://github.com/dotnet/core/issues/XXXX) for your questions and comments.
|
||||
|
||||
## Docker Images
|
||||
|
||||
The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have been updated for this release. Look for the updated images for .NET Core 2.1.1 and .NET Core SDK 2.1.301 and read ["Staying up-to-date with .NET Container Images"](https://blogs.msdn.microsoft.com/dotnet/2018/06/18/staying-up-to-date-with-net-container-images/) for details and insights into using the .NET Core images.
|
||||
|
||||
## Azure AppServices
|
||||
|
||||
* Deployment of .NET Core 2.1.1 to Azure App Services has begun. It will be available in limited regions today and expected worldwide by the end of the week.
|
||||
|
||||
## .NET Core Lifecycle News
|
||||
|
||||
|
||||
|
||||
### Supported Linux version changes
|
||||
|
||||
No changes in supported versions this month. Ubuntu 17.10 will reach end-of-life in July and will be removed from the supported list at that time.
|
||||
|
||||
## Notable Changes in 2.1
|
||||
|
||||
### Linux installers
|
||||
|
||||
#### Installer changes
|
||||
|
||||
The .NET Core 2.1 release included Linux installer updates to support package manager update (eg `apt-get update`) functionality. With the release of 2.1.1, we can now see how it works. Each package manager has its own dialect and idiosyncracies so take the time to look into the particulars of your system. Here's an example using `dnf` on a Fedora 28 system.
|
||||
|
||||
First, you need to update the package database to determine if there are any updates. `dnf check-update` is useful in that it will provide a list of available updates without trying to install anything. To trim the list, we can do something like this ...
|
||||
|
||||
```bash
|
||||
$sudo dnf check-update | grep dotnet
|
||||
dotnet-sdk-2.1.x86_64 2.1.301-1 packages-microsoft-com-prod
|
||||
```
|
||||
|
||||
Now that we know there is an update available, our system can be upgraded with the following. If this is the first install, you would usd `install` rather than `upgrade`.
|
||||
|
||||
```bash
|
||||
$sudo dnf upgrade dotnet-sdk-2.1
|
||||
Last metadata expiration check: 0:08:41 ago on Tue 19 Jun 2018 09:24:49 AM PDT.
|
||||
Dependencies resolved.
|
||||
=======================================================================================================================
|
||||
Package Arch Version Repository Size
|
||||
=======================================================================================================================
|
||||
Upgrading:
|
||||
aspnetcore-runtime-2.1 x86_64 2.1.1-1 packages-microsoft-com-prod 29 M
|
||||
dotnet-host x86_64 2.1.1-1 packages-microsoft-com-prod 45 k
|
||||
dotnet-hostfxr-2.1 x86_64 2.1.1-1 packages-microsoft-com-prod 195 k
|
||||
dotnet-runtime-2.1 x86_64 2.1.1-1 packages-microsoft-com-prod 27 M
|
||||
dotnet-runtime-deps-2.1 x86_64 2.1.1-1 packages-microsoft-com-prod 2.8 k
|
||||
dotnet-sdk-2.1 x86_64 2.1.301-1 packages-microsoft-com-prod 109 M
|
||||
|
||||
Transaction Summary
|
||||
=======================================================================================================================
|
||||
Upgrade 6 Packages
|
||||
|
||||
Total download size: 165 M
|
||||
Is this ok [y/N]:
|
||||
```
|
||||
|
||||
The package manager will install the updated version and remove the previous from your system. This is a change from previous installations which would leave the old versions behind. If a previous release of 2.1 is needed, it can be installed by explicitly referencing the version. Sticking with the Fedora example, you would use `dnf --showduplicates.`
|
||||
|
||||
```bash
|
||||
$dnf --showduplicates list dotnet-sdk-2.1
|
||||
Last metadata expiration check: 0:15:00 ago on Tue 19 Jun 2018 09:25:25 AM PDT.
|
||||
|
||||
Installed Packages
|
||||
dotnet-sdk-2.1.x86_64 2.1.301-1 @packages-microsoft-com-prod
|
||||
|
||||
Available Packages
|
||||
dotnet-sdk-2.1.x86_64 2.1.300-1 packages-microsoft-com-prod
|
||||
dotnet-sdk-2.1.x86_64 2.1.301-1 @packages-microsoft-com-prod
|
||||
```
|
||||
|
||||
You can see that 2.1.300 and 2.1.301 are available and 2.1.301 is currently installed. `dnf install dotnet-sdk-2.1-2.1.300-1` will downgrade the system from 2.1.301 to 2.1.300.
|
||||
Loading…
Reference in a new issue