57 lines
2.6 KiB
Markdown
57 lines
2.6 KiB
Markdown
|
# .NET Core 2.1 RC 1 Known Issues
|
||
|
|
||
|
This document lists known issues for **.NET Core 2.1 RC 1** which may be encountered during usage.
|
||
|
|
||
|
## Runtime
|
||
|
|
||
|
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.
|
||
|
|
||
|
*Workaround* - Clear $TMPDIR or set to a valid location.
|
||
|
|
||
|
## Global Tools
|
||
|
|
||
|
[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.
|
||
|
|
||
|
**Global Tools must target .NET Core Runtime 2.1 or higher** ([cli/9073](https://github.com/dotnet/cli/issues/9073))
|
||
|
|
||
|
*Workaround* - Upgrade to target .NET Core Runtime 2.1
|
||
|
|
||
|
** Global tools install succeeds on Mac and Linux but fails to run **
|
||
|
|
||
|
[cli/9319](https://github.com/dotnet/cli/issues/9319)
|
||
|
|
||
|
Installing a Global Tool using --tool-path with a relative path on Mac and Linux will succeed, but execution of the tool fails with error “The application to execute does not exist”.
|
||
|
|
||
|
This occurs because the relative path is calculated incorrectly.
|
||
|
|
||
|
*Workaround - Specify the full path for the --tool-path option. For example
|
||
|
|
||
|
- `dotnet tool install dotnetsay --tool-path /home/build/tools`
|
||
|
|
||
|
or use `pwd utility`
|
||
|
|
||
|
- `dotnet tool install dotnetsay --tool-path $(pwd)/tools`
|
||
|
|
||
|
### Installing on Linux using the installers installs the latest available dotnet-host package
|
||
|
|
||
|
There is an issue with dotnet-host 2.1.0-preview2-26406-04-1 which introduces a dependency incompatibility. [core-setup/issues/2128](https://github.com/dotnet/core-setup/issues/4007). This is only a problem when installing a previous version of .NET Core on a clean machine. For example, if you installed dotnet-runtime-2.0.6, the RC 1 host will be installed but not the rest of RC 1.
|
||
|
|
||
|
We have temporarily removed the RC 1 installers from the Linux package feeds until this is fully resolved.
|
||
|
|
||
|
**Workaround** - If you have gotten into this state, downgrade the dotnet-host pacakge to an older version.
|
||
|
|
||
|
```bash
|
||
|
sudo apt install dotnet-host=2.0.6-1
|
||
|
```
|