Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
77 lines (41 sloc) 4.16 KB

2.0.0 Preview 2 Known Issues

This document lists known issues for .NET Core 2.0.0 Preview 2 and .NET Core SDK 2.0.0 Preview 2 which may be encountered during usage.

Ubuntu - Uninstall Preview 1 before attempting to install Preview 2

Reported in 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

Visual Studio for the Mac

Visual Studio for the 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 Preview

https://github.com/aspnet/Tooling/blob/master/known-issues-vs2017-preview.md

Preview 1 issues which have been resolved

Running 1.0 first run experience after installing 2.0 CLI

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

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

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 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.
  2. Download the VSIX for the latest C# Extension.
  3. Follow the instructions from 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.

You can’t perform that action at this time.