2.0 RTM changes for whatsnew #3934
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scottaddie
requested changes
Aug 12, 2017
aspnetcore/aspnetcore-2.0.md
Outdated
| @@ -15,57 +15,35 @@ uid: aspnetcore-2.0 | |||
|
|
|||
| # What's new in ASP.NET Core 2.0 Preview | |||
There was a problem hiding this comment.
Remove the word "Preview" from the title
aspnetcore/aspnetcore-2.0.md
Outdated
|
|
||
| ## ASP.NET Core metapackage | ||
|
|
||
| A new ASP.NET Core metapackage includes all of the packages made and supported by the ASP.NET Core and Entity Framework Core teams, along with their internal and 3rd-party dependencies. You no longer need to choose individual ASP.NET Core features by package. All features are included in the [Microsoft.AspNetCore.All](https://www.nuget.org/packages/Microsoft.AspNetCore.All) package. The default templates use this package. | ||
|
|
||
| The version number of the `Microsoft.AspNetCore.All` metapackage represents the latest ASP.NET Core version (aligned with the .NET Core version). | ||
| For more information, see [Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.x](xref:fundamentals/metapackage). |
aspnetcore/aspnetcore-2.0.md
Outdated
|
|
||
| If there are features you don’t use in your application, the new package trimming features will exclude those binaries in the published application output. | ||
| Applications that use the `Microsoft.AspNetCore.All` metapackage automatically take advantage of the new .NET Core Runtime Store. The Store contains all the runtime assets needed to run ASP.NET Core 2.0 applications. When you use the `Microsoft.AspNetCore.All` metapackage, no assets from the referenced ASP.NET Core NuGet packages are deployed with the application because they already reside on the target system. The assets in the Runtime Store are also precompiled to improve application startup-time. |
There was a problem hiding this comment.
Remove dash between "startup" and "time"
aspnetcore/aspnetcore-2.0.md
Outdated
| @@ -74,7 +52,9 @@ For information about the status of planned documentation, see the [GitHub issue | |||
|
|
|||
| ## Logging update | |||
|
|
|||
| In ASP.NET 2.0, logging is incorporated into the dependency injection (DI) system by default. You add providers and configure filtering in the *Program.cs* file instead of in the *Startup.cs* file. And the default `ILoggerFactory` supports filtering in a way that lets you use one flexible approach for both cross-provider filtering and specific-provider filtering. For more information, see [Introduction to Logging](xref:fundamentals/logging). | |||
| In ASP.NET 2.0, logging is incorporated into the dependency injection (DI) system by default. You add providers and configure filtering in the *Program.cs* file instead of in the *Startup.cs* file. And the default `ILoggerFactory` supports filtering in a way that lets you use one flexible approach for both cross-provider filtering and specific-provider filtering. | |||
There was a problem hiding this comment.
ASP.NET 2.0 --> ASP.NET Core 2.0
aspnetcore/aspnetcore-2.0.md
Outdated
| @@ -137,14 +121,12 @@ For information about the status of planned documentation, see the [GitHub issue | |||
|
|
|||
| ASP.NET Core has always helped HTMLEncode your content by default, but with the new version we’re taking an extra step to help prevent cross-site request forgery (XSRF) attacks: ASP.NET Core will now emit anti-forgery tokens by default and validate them on form POST actions and pages without extra configuration. | |||
There was a problem hiding this comment.
- HTMLEncode --> HTML encode
- Convert the colon after "attacks" to a period
aspnetcore/aspnetcore-2.0.md
Outdated
|
|
||
| ## Automatic precompilation | ||
|
|
||
| Razor view pre-compilation is enabled during publish by default, reducing the publish output size and application startup time. | ||
|
|
||
| For information about the status of planned documentation, see the [GitHub issue](https://github.com/aspnet/Docs/issues/3547). | ||
|
|
||
| ## Razor support for C# 7.1 | ||
|
|
||
| The Razor engine has been updated to work with the new Roslyn compiler. That includes support for C# 7.1 features like Default Expressions, Inferred Tuple Names, and Pattern-Matching with Generics. To use C #7.1 in your project, add the following property in your project file and then reload the solution: |
There was a problem hiding this comment.
- Razor engine --> Razor view engine
- Remove extra space before "To use"
- C Review Request #7.1 --> C# 7.1
|
@tdykstra The word "Preview" will also need to be removed from the TOC node. |
scottaddie
approved these changes
Aug 12, 2017
Rick-Anderson
changed the title
tdykstra
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Review URL
@Rick-Anderson @scottaddie Ready for review but wait on merging