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

Merge pull request #810 from leecow/master

Browse source 
add 2.0 release and known issues docs
This commit is contained in:
Lee Coward 2017-08-14 08:42:55 -07:00 committed by GitHub
parent e5eb6bd63b 724cd487e5
commit f3c64ec2d7
2 changed files with 188 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

124
release-notes/2.0/2.0.0-known-issues.md Normal file
View file

@ -0,0 +1,124 @@
# .NET Core 2.0.0 Known Issues
This document lists known issues for *.NET Core 2.0.0* and *.NET Core SDK 2.0.0* which may be encountered during usage.
### Ubuntu - Uninstall Preview releases before attempting to install .NET Core 2.0.0
Reported in [dotnet/core/issues/717](https://github.com/dotnet/core/issues/717) If you have .NET Core Preview 1 installed, it will need to be removed before attempting to install Preview 2. This can be done by running the following command.
`sudo apt remove dotnet-dev-2.0.0-preview1-005977` for Preview 1
or
`sudo apt remove dotnet-dev-2.0.0-preview2-006497` for Preview 2.
## Docker restore failure when running from /
Dotnet restore fails when a project has been created at the linux root without having specified a name for the project.
If you do dotnet new {template name} at the linux root and do not specify a name for the project (using the -n or --name parameters), the project will be created without a name (resulting in a project called ".csproj" or a similar name for F# or VB). This creates a couple of notable - the project file will be "hidden" and dotnet restore will fail (as projects are required to have a non-empty name).
## Install requirements changed when installing from tar.gz
Changes in the .NET Core CLI first run behavior need to be executed in locations which the user has change permissions. For this reason, guidance for installing from binary archive on Linux and Mac has changed from /opt/dotnet to ~/dotnet and the dotnet directory must be created with user permissions rather than as sudo.
If the user does not have permissions to the dotnet directory when attempting to run a dotnet command for the first time a number of permissions errors will result.
More info: [dotnet/docs/issues/2790](https://github.com/dotnet/docs/issues/2790) and [dotnet/cli/issues/7203](https://github.com/dotnet/cli/issues/7203)
## NuGet disabled source are still used by dotnet.exe and msbuild
[content TBD]
## RHEL and the Runtime Package Store
Runtime Package Store is not available by default on Red Hat Enterprise Linux.
Description and work arounds in https://github.com/dotnet/designs/issues/10
Other details in https://github.com/aspnet/Coherence-Signed/issues/428 and https://github.com/aspnet/MetaPackages/issues/149
## Orphaned fallback folder in the user directory from Preview installation
As for the fallback folder in the user directory, we no longer use this nor modify the nuget.config to contain it. But we also do not attempt to go in and delete the entry that might have been created by a prerelease version that did. You should delete it in that case. The build will pull in the real fallback folder by a different mechanism (msbuild properties) that does not require modifying nuget.config.
More info: [dotnet/cli/issues/7416](https://github.com/dotnet/cli/issues/7416)
## Minimum NETCore.App requirements for .NET Core CLI
Because the .NET Core CLI is itself .NET Core application, it has minimum version requirements for NETCore.App.
* .NET CLI 1.0 -> NETCore.App 1.0.5
* .NET CLI 2.0 -> NETCore.App 1.1.2
## Visual Studio for the Mac
[Visual Studio for the Mac](https://www.visualstudio.com/vs/visual-studio-mac/) 7.1 (build 1258) was recently released into beta and supports .NET Core 2.0 Preview 2.
## NETStandard 2.0 and the .NET Framework
When referencing a NETStandard2.0 library from a .NETFramework application you must add a reference to the NETStandard.Library.NETFramework package to the .NETFramework project.
## .NET Core 2.0 and Visual Studio 2017 15.3
[Known issues in Visual Studio](https://github.com/aspnet/Tooling/blob/master/known-issues-vs2017.md)
## If user had x86 2.0 SDK installed and changed the path to use x86, issue will not happen
Dotnet has stopped working after start debugging when set 'Platform Target' to x86
https://devdiv.visualstudio.com/web/wi.aspx?pcguid=011b8bdf-6d56-4f87-be0d-0092136884d9&id=471295
## Preview issues which have been resolved
### Running 1.0 first run experience after installing 2.0 CLI
[https://github.com/dotnet/cli/issues/6550](https://github.com/dotnet/cli/issues/6550)
This fails because the 1.0 first run shells out two dotnet commands to do dotnet new and dotnet restore. Because this is a simple shell out, the 2.0 CLI ends up being picked up to execute the commands. However, in the 1.0 CLI, we invoke dotnet new passing –f netcoreapp1.0 and netcoreapp1.1 and the 2.0 CLI no longer carries these templates, which causes the command and the whole first run to fail.
#### Workarounds
* Run dotnet 1.0 first run experience before installing the 2.0 CLI by simply invoking 'dotnet new' in the command line after installing VS.
* Uninstalling the 2.0 CLI and then running 'dotnet new'.
* Putting a global.json pointing t 1.0 CLI in the root of the drive where you are executing the 1.0 command to trigger first run. Remember to remove it after the first run has been executed.
* Do nothing, in which case the first run will continue to run for 1.0 CLI and restore will hit the web.
### VB and .NET Core
There are a few issues with using VB and .NET Core to be aware of.
#### System.Data namespace contains no types warning
[https://github.com/dotnet/sdk/pull/1188](https://github.com/dotnet/sdk/pull/1188)
Creating a console\class library will build successfully but with a warning that System.Data namespace contains no types.
##### Workaround
Adding `<NoWarn>$(NoWarn),40057</NoWarn>` to the project will suppress the warning.
#### Packing a VB Library does not work
[https://github.com/NuGet/Home/issues/4886](https://github.com/NuGet/Home/issues/4886)
##### Workaround
Adding `<PackProjectInputFile>$(MSBuildProjectFile)</PackProjectInputFile>` to your `.vbproj` file and then invoking the Pack command will produce a package.
#### Unit Test Templates Do Not Exist
Unit test templates don’t exist in Preview 1 because test discovery fails for VB projects. This issue is under investigation and there is no workaround at this time.
#### Visual Studio for Mac
There are a [few items to be aware of](https://gist.github.com/mrward/70b8132003ef77d893111ecbea3e2225) if you are using .NET Core 2.0 with Visual Studio for Mac.
#### Visual Studio Code
If you want to try .NET Core 2.0 with Visual Studio Code, you will need to use an updated C# Extension.
1. If you haven't already, install [Visual Studio Code](https://code.visualstudio.com).
1. Download the VSIX for the [latest C# Extension](https://github.com/OmniSharp/omnisharp-vscode/releases/download/v1.10.0-beta2/csharp-1.10.0-beta2.vsix).
1. Follow the instructions from [Installing Beta Releases](https://github.com/OmniSharp/omnisharp-vscode/wiki/Installing-Beta-Releases). **Note:** If you already have C# for VS Code installed, you’ll want to uninstall it and relaunch VS Code before installing the beta.
If you try out the C# for VS Code bits and find any issues, please file them at [OmniSharp/omnisharp-vscode](https://github.com/OmniSharp/omnisharp-vscode/issues).

66
release-notes/2.0/2.0.0.md
View file

@ -1,3 +1,65 @@
# .NET Core 2.0.0 Release Notes - Coming Soon!
# .NET Core 2.0.0 Release Notes - August 14, 2017
We're busily working toward completing the .NET Core 2.0.0 release. This document is a placeholder.
.NET Core 2.0.0 and SDK 2.0.0 are available for download and testing.
* [Getting Started](https://www.microsoft.com/net/core/)
* [Downloads](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0.md)
The blog roundup
* [.NET Core](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/)
* [NETStandard2](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-standard-2-0/)
* [ASP.NET Core](https://blogs.msdn.microsoft.com/webdev/2017/08/14/announcing-asp-net-core-2-0/)
* [EF Core](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-entity-framework-core-2-0/)
The .NET Core SDK 2.0.0 includes .NET Core 2.0.0 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.0.0, the following command will show that you're running version `2.0.0` of the tools.
`dotnet --version`
A [number of improvements and additions](2.0.0-commit.md) to .NET Core 2.0 by an [incredible array of folks](2.0.0-contributor.md). You can see details for other areas of the release in the [.NET Blog](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/) and have a look at [.NET Core 2.0.0 Known Issues](2.0.0-known-issues.md) document as there are a few things to be aware of before installing.
You're feedback is important and appreciated. We've created [dotnet/core ####](https://github.com/dotnet/core/issues/) for your questions and comments.
## .NET Core 2.0 Highlights
### NETStandard 2
An incredible number of APIs have been to NETStandard2. See [Announcing NETStandard2](https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-standard-2-0/) for details.
### Platform updates
We have an exciting addition to the supported platform line-up with SUSE. Debian and Fedora have released updates recently which are also supported in 2.0.
* [SUSE Linux Enterprise Server 12 SP2](https://www.suse.com/products/server/)
* [Debian 9](https://www.debian.org/News/2017/20170617)
* [Fedora 25 and 26](https://getfedora.org)
#### High Sierra
.NET 2.0 has been testedon macOS High Sierra to ensure compatibility. Please start an conversation in #### if issues are encountered.
### Docker Images
The [.NET Core Docker images](https://hub.docker.com/r/microsoft/dotnet/) have been updated for this release. Look for the 2.0.0 images.
### Installer Package Name Changes
We received much feedback that our names and versions were confusing and generally messy. Great discussions were had with contributors to craft a plan which is implemented in Preview 2. You can see the conversation and details in [dotnet/designs/issues/2](https://github.com/dotnet/designs/issues/2) and [dotnet/core-setup/issues/1599](https://github.com/dotnet/core-setup/issues/1599).
### Server Hosting Bundles
Because the Runtime Package Store contains crossgen'ed files for a specific release, the hosting bundles will now install side-by-side. This will allow for previous applications to retain the performance benefits while applications targeting new Core versions will at the same time make use of the updated Store.
### Support
https://github.com/dotnet/core/blob/master/microsoft-support.md
https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md
https://github.com/dotnet/core/blob/master/release-notes/2.0/2.0-supported-os.md
### WCF
The [WCF release page](https://github.com/dotnet/wcf/releases/tag/v2.0.0) has details on fixes from the WCF team.
## ASP.NET Core
Please see the [ASP.NET Core release notes](https://github.com/aspnet/Home/releases/tag/2.0.0) and [ASP.NET Core announcement](######) for highlights on work from ASP.NET Core, MVC, Entity Framework Core and others.