Update known-issues-vs2017.md for VS 15.3 RTW (#1055)
Update known-issues-vs2017.md for VS 15.3 RTW
This commit is contained in:
Balamurugan Chirtsabesan
Andrew Hall
Родитель
46accc8b10
Коммит
ed2a4b33d0
|
|
@ -13,6 +13,13 @@ For known issues with .NET Core, use the following links to see the issues in th
|
|||
* [IDE/Project System](https://github.com/dotnet/roslyn-project-system/issues?q=is%3Aissue+label%3ABug+is%3Aopen)
|
||||
* [NuGet](https://github.com/NuGet/Home/issues?q=is%3Aissue+label%3AType%3ABug+is%3Aopen)
|
||||
|
||||
### Publishing a project with a reference can sometimes result in the referenced project getting published with the wrong configuration
|
||||
|
||||
* #### Issue:
|
||||
For a .NET Core Console project with a project reference to a Core / NET Standard Class Lib, if we publish the console app in release configuration, the class lib assembly will be published with Debug configuration instead. The console assembly will be in Release configuration as expected.
|
||||
|
||||
* #### Workaround:
|
||||
|
||||
### Publish .NET Core Console applications / class libraries
|
||||
|
||||
* #### Issue:
|
||||
|
|
@ -42,6 +49,16 @@ Only add one runtime identifier to the project, by changig the RuntimeIdentifier
|
|||
|
||||
## ASP.NET and Web Tools Known Issues
|
||||
|
||||
### When trying to publish to Azure, unable to create App Service for a project with _ in the project name
|
||||
|
||||
* #### Issue:
|
||||
When trying to publish a project with _ in the project name to Azure, the App Name text box of the Create App Service dialog can give a validation error: "Could not verify name availability, please try again"
|
||||
|
||||
|
||||
|
||||
* #### Workaround:
|
||||
Remove _ from the App Name text box
|
||||
|
||||
### MVC4 projects do not connect to SQL Server LocalDB at runtime
|
||||
|
||||
* #### Issue:
|
||||
|
|
@ -60,6 +77,97 @@ Use Visual Studio 2015 to profile, Azure App Services does not yet support profi
|
|||
|
||||
## ASP.NET Core Known Issues
|
||||
|
||||
### Re-targeting ASP.NET Core 1.0 or 1.1 application to ASP.NET Core 2.0 will require additional steps by the user
|
||||
|
||||
* #### Issue:
|
||||
After you change target of an existing ASP.NET Core 1.0 or 1.1 application to 2.0, you might get incompatibility errors. Here are some symptoms of issues you might see:
|
||||
|
||||
Build warning:
|
||||
```
|
||||
Package 'Microsoft.Composition 1.0.27' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project.
|
||||
```
|
||||
|
||||
Error when you run the project:
|
||||
```
|
||||
An unhandled exception occurred while processing the request.
|
||||
InvalidOperationException: Can not find compilation library location for package 'Microsoft.NETCore.App'
|
||||
Microsoft.Extensions.DependencyModel.CompilationLibrary.ResolveReferencePaths()
|
||||
```
|
||||
|
||||
Build Errors
|
||||
```
|
||||
error NU1605: Detected package downgrade: System.Diagnostics.Tools from 4.3.0 to 4.0.1. Reference the package directly from the project to select a different version.
|
||||
error NU1605: WebApplication1 (>= 1.0.0) -> Microsoft.VisualStudio.Web.BrowserLink (>= 1.1.2) -> Microsoft.AspNetCore.Hosting.Abstractions (>= 1.1.2) -> NETStandard.Library (>= 1.6.1) -> System.Diagnostics.Tools (>= 4.3.0)
|
||||
```
|
||||
|
||||
* #### Workaround:
|
||||
You will need to do additional steps to fully migrate your project to 2.0. See following documentation for additional details:
|
||||
|
||||
[Migrating from ASP.NET Core 1.x to ASP.NET Core 2.0](https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/)
|
||||
|
||||
[Migrating Authentication and Identity to ASP.NET Core 2.0](https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/identity-2x)
|
||||
|
||||
|
||||
### PackageManagerConsole EF Core commands like Add-Migration commands fail when a restore is in progress
|
||||
|
||||
* #### Issue:
|
||||
When a package restore is in progress, if you try to run one of the EntityFrameworkCore commands like Add-Migration and Update-Database using the Package Manager Console, it may fail with the following error
|
||||
|
||||
```
|
||||
Update-Database : The term 'Update-Database' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
|
||||
included, verify that the path is correct and try again.
|
||||
```
|
||||
|
||||
* #### Workaround:
|
||||
Wait until package restore completes and try again
|
||||
|
||||
### Edit and continue dialog pops up twice when debugging a Razor view
|
||||
|
||||
* #### Issue:
|
||||
When debugging a Razor view and / or hitting an exception in a Razor view the edit/continue dialog pops up in VisualStudio. If you click edit => f5, you will get the same prompt again.
|
||||
|
||||
* #### Workaround:
|
||||
Hit edit => close the Razor editor => f5.
|
||||
|
||||
|
||||
### When running dotnet aspnet-codegenerator from a command prompt, you run into an unhandled InvalidOperationException
|
||||
|
||||
* #### Issue:
|
||||
When you try to invoke dotnet aspnet-codegenerator after creating a new ASP.NET Core application using the command-line, you get an unhandled InvalidOperationException that mentions that Microsoft.VisualStudio.Web.CodeGeneration.Design package needs to be added as a NuGet package reference
|
||||
|
||||
Example:
|
||||
```
|
||||
dotnet new mvc
|
||||
dotnet aspnet-codegenerator
|
||||
```
|
||||
|
||||
|
||||
* #### Workaround:
|
||||
Add the missing package reference in your csproj file, and then run 'dotnet restore'
|
||||
|
||||
```
|
||||
<PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.0" />
|
||||
```
|
||||
|
||||
### EntityFramework migrations not available to be applied during publish
|
||||
|
||||
* #### Issue:
|
||||
Publish settings dialog for ASP.NET core web applications on .NET framework sometimes shows the EF migration section as empty when IIS express is running. This is because the files are locked and EF is not able to detect the dbcontexts for the project.
|
||||
|
||||
* #### Workaround:
|
||||
Exit the Publish dialog, do a VS build and re-open the publish settings dialog.
|
||||
|
||||
### Creating ASP.NET Core Web Application on .NET Framework may not work offline
|
||||
|
||||
* #### Issue:
|
||||
When creating a ASP.NET Core Web Application on .NET Framework without an internet connection, project creation may fail with the following package restore error due to missing ManagedEsent package
|
||||
|
||||
|
||||
|
||||
* #### Workaround:
|
||||
Connect to the internet and run Restore Packages on the solution
|
||||
|
||||
|
||||
### After installing update to Visual Studio and publishing a ASP.NET Core 1.1 application, you get a HTTP Error 502.5 on the published application
|
||||
|
||||
* #### Issue:
|
||||
|
|
@ -74,7 +182,7 @@ Install the 1.1.2 runtime on the web server
|
|||
Razor Tag Helpers do not get colorization or special IntelliSense at design time. They work normally at runtime.
|
||||
|
||||
* #### Workaround:
|
||||
Install the [Razor Language Service extension](https://aka.ms/razorlangsvc).
|
||||
Update VS 2017 to version 15.3
|
||||
|
||||
### No suggestions to install missing packages
|
||||
|
||||
|
|
@ -84,19 +192,21 @@ Pressing Ctrl+. on unresolved references to extension methods does not provide a
|
|||
* #### Workaround:
|
||||
Manually find and install the package using Manage NuGet packages UI
|
||||
|
||||
### NuGet Recommends Upgrading Packages in 1.0 app to 1.1 versions
|
||||
### NuGet Recommends Upgrading Packages in 1.0 / 1.1 app to 2.0 versions
|
||||
|
||||
* #### Issue:
|
||||
If your application is targeting ASP.NET Core 1.0 and you try to add NuGet packages using Manage NuGet Packages dialog or the Package Manager Console tool window, it defaults to installing the 1.1 version of the packages causing undesirable behavior in some cases.
|
||||
If your application is targeting ASP.NET Core 1.0 or 1.1 and you try to add NuGet packages using Manage NuGet Packages dialog or the Package Manager Console tool window, it defaults to installing the 2.0 version of the packages causing undesirable behavior in some cases.
|
||||
|
||||
* #### Workaround:
|
||||
Update the version of the packages to 1.0.x
|
||||
Update the version of the packages to 1.0.x / 1.1.x
|
||||
|
||||
### .NET Core project containing node_modules cause VS to hang
|
||||
|
||||
* #### Issue: Visual Studio becomes unresponsive when working on .NET Core projects that contain node_modules.
|
||||
* #### Issue:
|
||||
Visual Studio becomes unresponsive when working on .NET Core projects that contain node_modules.
|
||||
|
||||
* #### Workaround: Do npm restore while the project or VS is closed, and then reopen the solution/project.
|
||||
* #### Workaround:
|
||||
Do npm restore while the project or VS is closed, and then reopen the solution/project.
|
||||
|
||||
|
||||
### Publishing project with Entity Framework migration fails
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче