Merge branch 'master' into andrehal-janupdate
This commit is contained in:
Andrew-MSFT
GitHub
Коммит
f6b212c606
Двоичные данные
images/vs2017-ambiguity-error.png
Двоичные данные
images/vs2017-ambiguity-error.png
Двоичный файл не отображается.
|
До Ширина: | Высота: | Размер: 51 KiB |
|
|
@ -1,4 +1,43 @@
|
|||
# Known issues for Web Tools, and ASP.NET and ASP.NET/.NET Core in Visual Studio 2017
|
||||
# Known issues for ASP.NET and Web Tools in Visual Studio 2017
|
||||
|
||||
## Web Tools Known Issues
|
||||
|
||||
### <a href="#iisexpress"></a>ASP.NET projects fail to load after installing Visual Studio 2017 RC Update
|
||||
Web projects fail to launch with the messages such as : ``` The web project '[project name]' is configured to use IIS Express. You must download and install IIS Express in order to load this project ``` or ``` Initializing the applicationhost.config file failed. Cannot find IIS Express ```
|
||||
|
||||
Creation of an ASP.NET project fails with messages such as: ``` Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL)) ```
|
||||
|
||||
* #### Issue:
|
||||
A bug in the [12/12 Update](https://blogs.msdn.microsoft.com/webdev/2016/12/12/new-updates-to-web-tools-in-visual-studio-2017-rc) to Visual Studio 2017 RC uninstalls IIS Express during the update.
|
||||
|
||||
* #### Workaround:
|
||||
[Download and install IIS Express 10.0](https://www.microsoft.com/en-us/download/details.aspx?id=48264)
|
||||
|
||||
[*Update 12/15*] : The bug is now fixed in the [12/15 Update](https://blogs.msdn.microsoft.com/webdev/2016/12/12/new-updates-to-web-tools-in-visual-studio-2017-rc) to Visual Studio 2017 RC
|
||||
|
||||
### Unable to publish ASP.NET projects after installing Visual Studio 2017 RC Update
|
||||
|
||||
Publishing ASP.NET projects gives errors such as: ``` Microsoft Web Deploy is not correctly installed on this machine. Microsoft Web Deploy v3 or higher is recommended ```
|
||||
|
||||
* #### Issue:
|
||||
A bug in the [12/12 Update](https://blogs.msdn.microsoft.com/webdev/2016/12/12/new-updates-to-web-tools-in-visual-studio-2017-rc) to Visual Studio 2017 RC uninstalls Web Deploy during the update.
|
||||
|
||||
* #### Workaround:
|
||||
Download and [install Web Deploy 3.6](https://www.microsoft.com/en-us/download/details.aspx?id=43717).
|
||||
|
||||
[*Update 12/15*] : The bug is now fixed in the [12/15 Update](https://blogs.msdn.microsoft.com/webdev/2016/12/12/new-updates-to-web-tools-in-visual-studio-2017-rc) to Visual Studio 2017 RC
|
||||
|
||||
### Unable to connect to SQL Server 2016 LocalDb after installing Visual Studio 2017 RC Update
|
||||
|
||||
Working with a LocalDb database gives errors such as: ``` A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. ``` or ``` Unable to locate a Local Database Runtime installation. Verify that SQL Server Express is properly installed and that the Local Database Runtime feature is enabled ```
|
||||
|
||||
* #### Issue:
|
||||
A bug in the [12/12 Update](https://blogs.msdn.microsoft.com/webdev/2016/12/12/new-updates-to-web-tools-in-visual-studio-2017-rc) to Visual Studio 2017 RC uninstalls SQL Server 2016 LocalDb during the update.
|
||||
|
||||
* #### Workaround:
|
||||
Download and install [SQL Server 2016 LocalDb](https://www.microsoft.com/en-us/download/details.aspx?id=54284).
|
||||
|
||||
[*Update 12/15*] : The bug is now fixed in the [12/15 Update](https://blogs.msdn.microsoft.com/webdev/2016/12/12/new-updates-to-web-tools-in-visual-studio-2017-rc) to Visual Studio 2017 RC
|
||||
|
||||
## .NET Core Known Issues
|
||||
For known issues with .NET Core, using the following links to see the issues in the .NET Core GitHub repo the team is tracking including comments and status.
|
||||
|
|
@ -37,6 +76,17 @@ When creating an ASP.NET Core project, if you check the "Enable Container (Docke
|
|||
* #### Workaround:
|
||||
Install [Docker for Windows](https://docs.docker.com/docker-for-windows/) to resolve the issue
|
||||
|
||||
### Error when opening ASP.NET Core project
|
||||
Error dialog with message : The project system has encountered an error. Could not resolve mscorlib for target framework '.NETCoreApp,Version=v1.0'
|
||||
|
||||
* #### Issue:
|
||||
When you create or re-open an ASP.NET Core project, you might sometimes see this error dialog:
|
||||
|
||||
The project system has encountered an error. Could not resolve mscorlib for target framework '.NETCoreApp,Version=v1.0'
|
||||
|
||||
* #### Workaround:
|
||||
Restart Visual Studio and try again
|
||||
|
||||
### No suggestions to install missing packages
|
||||
Ctrl+. Light Bulbs does not work with extension methods in .NET Core or ASP.NET Core projects
|
||||
|
||||
|
|
@ -64,6 +114,15 @@ TypeScript files are not automatically compiled on save in .NET Core projects
|
|||
* #### Workaround:
|
||||
Add a tsconfig.json file to the root of the project, containing at least {}.
|
||||
|
||||
### Scaffolding broken
|
||||
Scaffolding broken for ASP.NET Core (.NET Framework) templates
|
||||
|
||||
* #### Issue:
|
||||
[CLI is not generating the assembly redirects for project dependency tools](https://github.com/dotnet/cli/issues/4666)
|
||||
|
||||
* #### Workaround:
|
||||
None
|
||||
|
||||
### Sequence numbers added to wronge item templates
|
||||
Sequence numbers are added to inappropriate Item Templates
|
||||
|
||||
|
|
@ -173,7 +232,7 @@ Cannot apply migrations during publish of ASP.NET Core project
|
|||
Ability to provide a destination connection string and apply migrations are not available in the Publish Settings for an ASP.NET Core project
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 01/26 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/webdev/2017/01/26/updates-to-web-tools-in-visual-studio-2017-rc/)
|
||||
You need to manually apply migrations on the destination database server
|
||||
|
||||
### Unable to publish
|
||||
Unable to publish ASP.NET Core Web Application (.NET Framework)
|
||||
|
|
@ -182,7 +241,7 @@ Unable to publish ASP.NET Core Web Application (.NET Framework)
|
|||
If you try to publish an ASP.NET Core Web Application (.NET Framework), you will run into the following error: "DestinationFiles" refers to 1 item(s), and "SourceFiles" refers to 2 item(s). They must have the same number of items
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 01/26 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/webdev/2017/01/26/updates-to-web-tools-in-visual-studio-2017-rc/)
|
||||
None available
|
||||
|
||||
### Publish crashes
|
||||
Publish crashes on locales that do not use '.' as a decimal separator
|
||||
|
|
@ -191,7 +250,7 @@ Publish crashes on locales that do not use '.' as a decimal separator
|
|||
A bug in publishing fails to distinguish decimal separators in a language-neutral way.
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 01/26 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/webdev/2017/01/26/updates-to-web-tools-in-visual-studio-2017-rc/)
|
||||
Before publishing, set VS locale to ENU.
|
||||
|
||||
### Cannot configure web server settings
|
||||
Property pages of ASP.NET Core projects do not allow you to configure Web Server Settings
|
||||
|
|
@ -200,7 +259,7 @@ Property pages of ASP.NET Core projects do not allow you to configure Web Server
|
|||
Web Server settings such as App URL, ability to enable SSL, Windows Authentication are not available in the property pages of an ASP.NET Core project
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 01/26 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/webdev/2017/01/26/updates-to-web-tools-in-visual-studio-2017-rc/)
|
||||
You can edit the launchSettings.json file and apply settings similar to .NET Core tooling in Visual Studio 2015
|
||||
|
||||
### Razor IntelliSense not working
|
||||
Razor IntelliSense Completion issues in .NET Core projects
|
||||
|
|
@ -209,7 +268,27 @@ Razor IntelliSense Completion issues in .NET Core projects
|
|||
Completion at the end of razor expressions doesn't work well in RC. eg, typing "@DateTi." or "@DateTime." (w/o the quotes) will not commit properly, and may mark the dot as markup. Please report any additional IntelliSense Issues using "Send Feedback."
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 01/26 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/webdev/2017/01/26/updates-to-web-tools-in-visual-studio-2017-rc/)
|
||||
Backspace one character and retry
|
||||
|
||||
### Scaffolded files not included in project
|
||||
Scaffolded files may not be included in user's project in certain cases, where user's project defines exclusions.
|
||||
|
||||
* #### Issue:
|
||||
If user project has a globbing pattern for ```<Compile>``` item group with a exclude pattern. And if the files generated by scaffolding match the pattern, they are not included in the project. For example: If project has ```<Compile Include = "**/*.cs" Exclude="ExcludedDir/*.cs" />``` and scaffolding generates a file in 'DefaultController.cs' ExcludedDir, it will not be included in the project for compilation.
|
||||
|
||||
* #### Workaround:
|
||||
Manually adjust the globbing pattern to include the 'ExcludedDir/DefaultController
|
||||
|
||||
### Bower packages fail to restore
|
||||
Bower Restore fails to restore packages
|
||||
|
||||
* #### Issue:
|
||||
Bower Restore does not function, and IntelliSense for version numbers in bower.json always returns "*". Attempt to restore displays the following in the Output Window (Bower/npm pane):
|
||||
|
||||
ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/lodash/lodash.git", exit code of #128
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 12/12 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/dotnet/2016/12/12/updating-visual-studio-2017-rc-net-core-tooling-improvements)
|
||||
|
||||
### Long time before all files are visible in Solution Explorer
|
||||
After creating a .NET Core or ASP.NET Core project, you need to wait until package restore completes
|
||||
|
|
@ -238,13 +317,3 @@ There is an error in the project template processing code, and $webserverport1$
|
|||
* #### Workaround:
|
||||
Install [the 12/12 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/dotnet/2016/12/12/updating-visual-studio-2017-rc-net-core-tooling-improvements)
|
||||
|
||||
### Bower packages fail to restore
|
||||
Bower Restore fails to restore packages
|
||||
|
||||
* #### Issue:
|
||||
Bower Restore does not function, and IntelliSense for version numbers in bower.json always returns "*". Attempt to restore displays the following in the Output Window (Bower/npm pane):
|
||||
|
||||
ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/lodash/lodash.git", exit code of #128
|
||||
|
||||
* #### Workaround:
|
||||
Install [the 12/12 update for Visual Studio 2017 RC](https://blogs.msdn.microsoft.com/dotnet/2016/12/12/updating-visual-studio-2017-rc-net-core-tooling-improvements)
|
||||
Загрузка…
Ссылка в новой задаче