maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge pull request #1629 from svick/patch-1

Browse source 
Fix formatting in 2.1 known issues
This commit is contained in:
Lee Coward 2018-05-31 08:15:01 -07:00 committed by GitHub
parent 8eb25a1400 1ad8604aff
commit 9b79753ac6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
release-notes/2.1/2.1.0-known-issues.md
View file

@ -4,7 +4,7 @@ This document lists known issues for **.NET Core 2.1 RC 1** which may be encount
## Runtime
core-setup/4149](https://github.com/dotnet/core-setup/issues/4149
[core-setup/4149](https://github.com/dotnet/core-setup/issues/4149)
On Unix, if $TMPDIR is set to a nonexistent or non writeable location, your app will log "Failed to initialize CoreCLR, HRESULT: 0x80004005" to the console and fail to start.
@ -28,7 +28,7 @@ Also: Ensure that global.json does not pin to .NET Core SDK 2.1.300 Preview 1 on
*Workaround* - Upgrade to target .NET Core Runtime 2.1
** Global tools install succeeds on Mac and Linux but fails to run **
**Global tools install succeeds on Mac and Linux but fails to run**
[cli/9319](https://github.com/dotnet/cli/issues/9319)
@ -36,7 +36,7 @@ Installing a Global Tool using --tool-path with a relative path on Mac and Linux
This occurs because the relative path is calculated incorrectly.
*Workaround - Specify the full path for the --tool-path option. For example
*Workaround* - Specify the full path for the --tool-path option. For example
- `dotnet tool install dotnetsay --tool-path /home/build/tools`
@ -54,4 +54,4 @@ We have temporarily removed the RC 1 installers from the Linux package feeds unt
```bash
sudo apt install dotnet-host=2.0.6-1
```
```