Lee Coward
GitHub
commit
31e0632def
53
Documentation/prereqs.md
Normal file
53
Documentation/prereqs.md
Normal file
|
|
@ -0,0 +1,53 @@
|
|||
.NET Core native prerequisites
|
||||
==============================
|
||||
|
||||
This document outlines the dependencies needed to run .NET Core tools and applications.
|
||||
|
||||
For Operating System support, please refer to [the roadmap document](https://github.com/dotnet/core/blob/master/roadmap.md#technology-roadmaps).
|
||||
|
||||
## Windows dependencies
|
||||
On Windows, the only dependency is the VC++ Redistributable. Depending on the version of Windows you are running on, the versions are changing.
|
||||
|
||||
> **Note:** these dependencies are chained in the installer, you only need to install them manually if you are using
|
||||
> the installer script (`dotnet-install.sh` or `dotnet-install.ps1`).
|
||||
|
||||
* Windows 10
|
||||
* [Visual C++ Redistributable for Visual Studio 2015](https://www.microsoft.com/en-us/download/details.aspx?id=48145)
|
||||
* Pre-Windows 10
|
||||
* Please make sure that your Windows installation is up-to-date and includes hotfix [KB2533623] (https://support.microsoft.com/en-us/kb/2533623) installed through Windows Update.
|
||||
* [Universal CRT update](https://www.microsoft.com/en-us/download/details.aspx?id=48234) (you can get more info on what Universal CRT is in [this blog post](https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt/))
|
||||
|
||||
## Ubuntu
|
||||
Ubuntu distributions require the following libraries installed:
|
||||
|
||||
- libunwind8
|
||||
- libunwind8-dev
|
||||
- gettext
|
||||
- libicu-dev
|
||||
- liblttng-ust-dev
|
||||
- libcurl4-openssl-dev
|
||||
- libssl-dev
|
||||
- uuid-dev
|
||||
- unzip
|
||||
|
||||
|
||||
## CentOS
|
||||
CentOS distributions require the following libraries installed:
|
||||
|
||||
* deltarpm
|
||||
* epel-release
|
||||
* unzip
|
||||
* libunwind
|
||||
* gettext
|
||||
* libcurl-devel
|
||||
* openssl-devel
|
||||
* zlib
|
||||
* libicu-devel
|
||||
|
||||
## OS X
|
||||
OS X requires the following libraries and versions installed:
|
||||
|
||||
* libssl version 1.0.1
|
||||
|
||||
## Installing the dependencies
|
||||
Please follow the recommended practices of each operating system in question. For Linux, we recommend using your package manager such as `apt-get` for Ubuntu and `yum` for CentOS. For OS X and upgrading the libssl, we recommend using [Homebrew](https://brew.sh/); if you do use it, do not forget the link phase you need to do at the end of install (`brew link openssl --force`).
|
||||
|
|
@ -7,7 +7,7 @@ The core repository is the starting point to engage in and learn about the
|
|||
|
||||
If you're new to .NET Core and have 10 minutes to try it, start here:
|
||||
- [What is .NET Core?](http://dotnet.github.io/about/)
|
||||
- [Get Started with .NET Core on Windows, OSX and Linux](http://dotnet.github.io/getting-started/)
|
||||
- [Get Started with .NET Core on Windows, OSX and Linux](https://www.microsoft.com/net/core)
|
||||
|
||||
If you have some more time and want to go deeper:
|
||||
- [Install ASP.NET Core on Windows, OSX and Linux](https://github.com/aspnet/home)
|
||||
|
|
|
|||
11
cli/README.md
Normal file
11
cli/README.md
Normal file
|
|
@ -0,0 +1,11 @@
|
|||
.NET Core Tools support documents
|
||||
=================================
|
||||
|
||||
This folder contains the support documents for the [.NET Core Command Line Tools](https://github.com/dotnet/cli). The purpose of this folder is to
|
||||
isolate those facts that are just pertinent to the said tools.
|
||||
|
||||
All other facts that appear in this repo and that pertain to .NET Core in general (for example, the supported OS-es or the native pre-requsities) should
|
||||
be considered to apply to the tools as well, unless otherwise noted.
|
||||
|
||||
* [Native pre-requisites](https://github.com/dotnet/core/blob/clidocsmo/Documentation/prereqs.md)
|
||||
* [Supported OS-es and roadmap](https://github.com/dotnet/core/blob/clidocsmo/roadmap.md)
|
||||
125
cli/known-issues.md
Normal file
125
cli/known-issues.md
Normal file
|
|
@ -0,0 +1,125 @@
|
|||
Known issues & workarounds
|
||||
==========================
|
||||
|
||||
## OpenSSL dependency on OS X
|
||||
OS X "El Capitan" (10.11) comes with 0.9.8 version of OpenSSL. .NET Core depends on versions >= 1.0.1 of OpenSSL. You can update the version by using [Homebrew](https://brew.sh), [MacPorts](https://www.macports.org/) or manually. The important bit is that you need to have the required OpenSSL version on the path when you work with .NET Core.
|
||||
|
||||
With Homebrew, you can run the following commands to get this done:
|
||||
|
||||
```console
|
||||
brew update
|
||||
brew install openssl
|
||||
brew link --force openssl
|
||||
```
|
||||
|
||||
Homebrew may also show the following warning:
|
||||
|
||||
> Apple has deprecated use of OpenSSL in favor of its own TLS and crypto libraries
|
||||
|
||||
This warning is meant for the software that uses OpenSSL (in this case, .NET Core) and not for the end-user that is installing said software. Homebrew installation doesn't touch either the existing Apple crypto libraries or existing OpenSSL 0.9.8 version, so there is no impact on any software that uses either one of those crypto solutions and is already installed.
|
||||
|
||||
MacPorts doesn't have the concept of linking, so it is reccomended that you uninstall 0.9.8 version of OpenSSL using the following command:
|
||||
|
||||
```console
|
||||
sudo port upgrade openssl
|
||||
sudo port -f uninstall openssl @0.9.8
|
||||
```
|
||||
|
||||
You can verify whether you have the right version using the `openssl version` command from the Terminal.
|
||||
|
||||
## Running .NET Core CLI on Nano Server
|
||||
|
||||
If you’re using Nano Server Technical Preview 5 with .NET Core CLI, due to a bug in the Nano Server product, you will need to copy binaries from `c:\windows\system32\forwarders`. The destination depends on the [type of deployment](https://dotnet.github.io/docs/core-concepts/app-types.html) that you are choosing for your application.
|
||||
|
||||
For portable applications, the forwarders need to be copied to the shared runtime location. The shared runtime can be found wherever you installed .NET Core (by default, it is `C:\Program Files\dotnet`) under the following path: `shared\Microsoft.NETCore.App\<version>\`.
|
||||
|
||||
For self-contained applications, the forwarders need to be copied over into the application folder, that is, wherever you put the published output.
|
||||
|
||||
This process will ensure that the `dotnet` host finds the appropriate APIs it needs. If your Nano Server Technical Preview 5 build is updated or serviced, please make sure to repeat this process, in case any of the forwarders have been updated as well.
|
||||
|
||||
Apologies for any inconvenience. Again, this has been fixed in later releases.
|
||||
|
||||
## Users of zsh (z shell) don't get `dotnet` on the path after install
|
||||
There is a known issue in oh-my-zsh installer that interferes with how `path_helper` works on OS X systems. In short,
|
||||
the said installer creates a `.zshrc` file which contains the exploded path at the time of installation. This clobbers
|
||||
any dynamically generated path, such as the one generated by `path_helper`.
|
||||
|
||||
There is an [outstanding PR](https://github.com/robbyrussell/oh-my-zsh/pull/4925) on the oh-my-zsh repo for this.
|
||||
|
||||
**Workaround 1:** symlink the `dotnet` binary in the installation directory to a place in the global path, e.g. `/usr/local/bin`.
|
||||
The command you can use is:
|
||||
|
||||
```console
|
||||
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin
|
||||
```
|
||||
|
||||
**Workaround 2:** edit your `.zshrc` and/or `.zshprofile` files to add the `/usr/local/share/dotnet` to the $PATH.
|
||||
|
||||
## On dev builds of the tools, restoring default project from dotnet new fails
|
||||
When using non-release versions of the CLI, `dotnet restore` will fail to restore `Microsoft.NETCore.App` because for that particular version it exists on a NuGet feed that is not configured on the machine. This behavior is by design and does not happen with public releases (such as RC2).
|
||||
|
||||
**Workaround:** create a `NuGet.config` file in the project directory which contains the following:
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<configuration>
|
||||
<packageSources>
|
||||
<!--To inherit the global NuGet package sources remove the <clear/> line below -->
|
||||
<clear />
|
||||
<add key="dotnet-core" value="https://dotnet.myget.org/F/dotnet-core/api/v3/index.json" />
|
||||
<add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
|
||||
</packageSources>
|
||||
</configuration>
|
||||
```
|
||||
|
||||
## `dotnet restore` times out on Win7 x64
|
||||
If you have any virtualization software (so far we've confirmed VMWare and Virtual Box) and you try to use the CLI on a Win7 SP1 x64 machine, `dotnet restore` will be really slow and will eventually time out without doing much restoring. The issue is in the virtual networking adapters that usually get installed with said software.
|
||||
|
||||
**Issues tracking this:**
|
||||
|
||||
* [#1732](https://github.com/dotnet/cli/issues/1732)
|
||||
|
||||
**Affects:** `dotnet restore`
|
||||
|
||||
**Workaround:** disable the virtual network interface and do the restore.
|
||||
|
||||
## Resolving the Standard library packages
|
||||
The StdLib package is on a MyGet feed. In order to restore it, a MyGet feed needs to be added
|
||||
to the NuGet feeds, either locally per application or in a central location.
|
||||
|
||||
**Issues tracking this:**
|
||||
|
||||
* [#535](https://github.com/dotnet/cli/issues/535)
|
||||
|
||||
**Affects:** `dotnet restore`
|
||||
|
||||
**Workaround:** update to the latest bits and run `dotnet new` in an empty directory. This will
|
||||
now drop a `nuget.config` file that you can use in other applications.
|
||||
|
||||
If you cannot update, you can use the following `nuget.config`:
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<configuration>
|
||||
<packageSources>
|
||||
<!--To inherit the global NuGet package sources remove the <clear/> line below -->
|
||||
<clear />
|
||||
<add key="dotnet-core" value="https://dotnet.myget.org/F/dotnet-core/api/v3/index.json" />
|
||||
<add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
|
||||
</packageSources>
|
||||
</configuration>
|
||||
```
|
||||
|
||||
## Uninstalling/reinstalling the PKG on OS X
|
||||
OS X doesn't really have an uninstall capacity for PKGs like Windows has for
|
||||
MSIs. There is, however, a way to remove the bits as well as the "recipe" for
|
||||
dotnet. More information can be found on [this SuperUser question](http://superuser.com/questions/36567/how-do-i-uninstall-any-apple-pkg-package-file).
|
||||
|
||||
# What is this document about?
|
||||
This document outlines the known issues and workarounds for the current state of
|
||||
the CLI tools. Issues will also have a workaround and affects sections if necessary. You can use this page to
|
||||
get information and get unblocked.
|
||||
|
||||
# What is a "known issue"?
|
||||
A "known issue" is a major issue that block users in doing their everyday tasks and that affect all or
|
||||
most of the commands in the CLI tools. If you want to report or see minor issues, you can use the [issues list](https://github.com/dotnet/cli/issues).
|
||||
|
|
@ -1002,7 +1002,7 @@ namespace System.Net.NetworkInformation {
|
|||
public NetworkInformationException(int errorCode);
|
||||
public int ErrorCode { get; }
|
||||
}
|
||||
public staticabstract class NetworkInterface {
|
||||
public static abstract class NetworkInterface {
|
||||
protected NetworkInterface();
|
||||
public virtual string Description { get; }
|
||||
public virtual string Id { get; }
|
||||
|
|
|
|||
2
release-notes/1.0/Release-Notes-1.0.0.md
Normal file
2
release-notes/1.0/Release-Notes-1.0.0.md
Normal file
|
|
@ -0,0 +1,2 @@
|
|||
#Release Notes
|
||||
TBD
|
||||
|
|
@ -12,10 +12,10 @@ There are a few issues to be aware of, which are described in the [.NET Core Kno
|
|||
### RC2 Platform Support
|
||||
|
||||
* Red Hat Enterprise Linux 7.2
|
||||
* Debian 8.2 (8.2, 8.3, 8.4)+
|
||||
* Debian 8.2+
|
||||
* Ubuntu 14.04 (16.04 support is coming in RTM)
|
||||
* OS X 10.11
|
||||
* Centos 7.1
|
||||
* Mac OS X 10.11
|
||||
* CentOS 7.1+
|
||||
* Windows 7+ / Server 2012 R2+
|
||||
* Windows Nano Server TP5
|
||||
|
||||
|
|
@ -143,4 +143,4 @@ The lists of issues closed for this and past releases can be found here:
|
|||
The lists of commits for this release can be viewed here:
|
||||
|
||||
* [CLR commits](https://github.com/dotnet/coreclr/commits/release/1.0.0-rc2)
|
||||
* [BCL commits](https://github.com/dotnet/corefx/commits/release/1.0.0-rc2)
|
||||
* [BCL commits](https://github.com/dotnet/corefx/commits/release/1.0.0-rc2)
|
||||
|
|
|
|||
2
release-notes/1.1/Release-Notes-1.1.0-beta.md
Normal file
2
release-notes/1.1/Release-Notes-1.1.0-beta.md
Normal file
|
|
@ -0,0 +1,2 @@
|
|||
# Release Notes
|
||||
TBD
|
||||
22
roadmap.md
22
roadmap.md
|
|
@ -23,14 +23,18 @@ Architecture:
|
|||
Version 1.0 OS Support:
|
||||
|
||||
OS|Version|Architectures|Configurations
|
||||
------------------------------|--------------------|----------|---
|
||||
Windows Client | 7 SP1 - 10 | x64, x86 |
|
||||
Windows Server | 2008 R2 SP1 - 2016 | x64, x86 | Full, Server Core, Nano (2016 only)
|
||||
Red Hat Enterprise Linux | 7.2 | x64 |
|
||||
Debian | 8.2 | x64 |
|
||||
Ubuntu | 14.04 LTS | x64 |
|
||||
Centos | 7.1 | x64 |
|
||||
Mac OSX | 10.11 (El Capitan) | x64 |
|
||||
------------------------------|-------------------------------|----------|---
|
||||
Windows Client | 7 SP1 - 10 | x64, x86 |
|
||||
Windows Server | 2008 R2 SP1 - 2016 | x64, x86 | Full, Server Core, Nano (2016 only)
|
||||
Red Hat Enterprise Linux | 7.2 | x64 |
|
||||
Fedora | 23 | x64 |
|
||||
Debian | 8.2 | x64 |
|
||||
Ubuntu | 14.04 LTS, 16.04 LTS | x64 |
|
||||
Linux Mint | 17 | x64 |
|
||||
openSUSE | 13.2 | x64 |
|
||||
Centos | 7.1 | x64 |
|
||||
Oracle Linux | 7.1 | x64 |
|
||||
Mac OSX | 10.11 (El Capitan) | x64 |
|
||||
|
||||
There will be packages available for the native package managers for each OS. (e.g. apt-get, rpm, pkg, msi) as well as zips.
|
||||
|
||||
|
|
@ -87,7 +91,7 @@ At Microsoft, .NET has always been an important component of other teams' produc
|
|||
|
||||
|Milestone|Release Date|
|
||||
|---------|------------|
|
||||
|RTM | |
|
||||
|RTM | 6/27/2016 |
|
||||
|
||||
Notes:
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ In order to run these samples, you first need to [install .NET Core](http://dotn
|
|||
* Compile and run using the following commands
|
||||
* `dotnet restore`
|
||||
* `dotnet build`
|
||||
* `./bin/Debug/[framework]/[binary name]`
|
||||
* `dotnet bin/Debug/[framework]/[binary name]`
|
||||
|
||||
## Samples list
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue