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

add vb issues to known issues doc

Browse source
This commit is contained in:
Lee Coward 2017-05-10 13:42:03 -07:00
parent 10e835ef47
commit c39f1b8451
1 changed files with 28 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
release-notes/2.0/2.0.0-preview1-known-issues.md
View file

@ -4,17 +4,39 @@ This document lists known issues for *.NET Core 2.0.0 Preview 1* and *.NET Core
## Running 1.0 first run experience after installing 2.0 CLI ## Running 1.0 first run experience after installing 2.0 CLI
**Tracking issue**
[https://github.com/dotnet/cli/issues/6550](https://github.com/dotnet/cli/issues/6550) [https://github.com/dotnet/cli/issues/6550](https://github.com/dotnet/cli/issues/6550)
**Description**
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. 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** ### 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. * 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'. * 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. * 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. * 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.