Fixes#11232
This heading ...
> \#\# Moving from WebHostBuilder to HostBuilder
... didn't seem to make sense because the prior section is addressing the same migration aspect. These two sections were probably added at different times (guessing), which would explain the (accidental) appearance of both.
I see a handful of little super-nits in the view comp file beyond the few that I touch here (mostly punctuation on this PR), but I'll leave those unless you want me to edit the file.
Fix https://github.com/aspnet/Docs/issues/10636
### Question
@Rick-Anderson
Under 7f52e7646a/aspnetcore/mvc/views/view-components.md (specifying-a-view-name)
I don't know why there is the sentance`Update Views/ToDoList/Index.cshtml:` Maybe we must say instead `Update Views/ToDo/Index.cshtml:`
Furthermore, there is a comment ` <!-- Views/ToDoList/Index.cshtml is never imported, so change to test tutorial -->` . But the Views/TodoList doesn't exist ? Should we delete this comment?
Sorry, I don't understand well…
* Update About.cshtml
The WebsiteContext instance was initialized inside a C# code block to avoid a possible problem when one of its attributes is a string.
* Update authoring.md
Update highlights and ranges after updating the relevant source code:
authoring/sample/AuthoringTagHelpers/src/AuthoringTagHelpers/Views/Home/About.cshtml
* Add example of asp-area with a Razor Pages area
* Minor edits
* Fix code snippet include
* Add example of AllowAreas property
* Update aspnetcore/mvc/views/tag-helpers/built-in/anchor-tag-helper.md
Co-Authored-By: scottaddie <10702007+scottaddie@users.noreply.github.com>
Fixes#9336
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
Fixes#6971
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
* overview
* whats new to end
* fix migration node
* split fundamentals, move to end
* glob & loc, get started
* security node name
* security section
* azure, client-side, host
* several more sections
* redistribute tutorials
* proofread fixes
* move how to download section
* index files delete and redirect
* fix errors
* reorder some nodes
* scott feedback, flatten main tutorials node
* fix missed feedback items + other issues
* unflatten tutorials node
* move 'how to download'
* more tutorials node tweaks
* standardize view sample links
* db --> DB
* fix build error
* remove link from a parent node
* streamline node names
* xref links
* typos
* typo
* typos and revert some xref links
* scott feedback
* scott feedback
* feedback
* change node name
* safe storage-->protect
Fixes#9219
@JunTaoLuo Dan calls out the implicit versioning "for 2.1 SDK or later;" however, we don't usually version the doc content by SDK release. We might need to say something for this update in the passage that I'm adding to the All topic (*aspnetcore/fundamentals/metapackage.md*) about which SDK version this applies to. I don't know if that's something that you would like to do or what version to call out.
I also remove the version from the samples. We also assume that devs are using the latest SDK with our samples.
I will not lie: this was not enjoyable. With the realization that this page might be shuffled around to a new spot in the TOC, it was a delicate act balancing Razor pages and traditional MVC without getting too intrusive about it.
As such, I:
* Included a note at the top of the document outlining the subtle differences, so I can just casually reference them later and don't have to explain which is which
* Replaced wording of "views" with "pages or views"
* Changed controller wording to "the folder where the handler method (or controller) exists."
I also updated the *_Layout.cshtml* sample file. It's a little different, two years later.
I expect some back-and-forth about this—let me know what you think, @Rick-Anderson.
Fixes#8030
Hello, @rick-anderson,
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
Description: Some of the "folder names" inside \<\> are not displaying well in localized pages, and also those terms are not blocked for localization.
Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR then share your PR number so we can confirm and close this PR.
Many thanks in advance.
Addresses #8579
I might be getting the hang of **_find and replace_** now. 😝
This doesn't touch a couple that ref 2.2.0. I'll tidy those up on https://github.com/aspnet/Docs/issues/8518 after 2.2 RTM.
Related to https://github.com/aspnet/Docs/pull/4599.
Removed unnecessary `@` symbols, added missing double quotes, and replaced inline code snippet with code import.
Hello, @rick-anderson ,
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
"The unescaped '@' sign is breaking the code"
Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR then share your PR number so we can confirm and close this PR.
Many thanks in advance.
I just tested and it does not matter whether the project in vs2017 is created with or without authentication regarding the _viewimports file. Seems odd it mentions that making the reader think that there is a difference or why would it be mentioned. Second ,and not sure if this should be addressed because it might be the tip of the iceberg, the files are no longer in views/ but are now in pages/
* UE edit of Razor file compilation doc
* More edits
* Include .NET Framework csproj file
* More edits
* Apply more versioning moniker changes
* More cleanup
Currently the highlight is mapping the operation of GetAveragePriority on the incorrect line:
[Statistics_Service.png](https://postimg.org/image/5m0gjw6bf/)
The correction is to highlight the previous line.
* Add model to TH sample
Without model it looks like the TH isn't doing anything other than changing `asp-for` into `for`.
* Tag Helpers intro doc patch (#5519)
* UE edit of Anchor Tag Helper doc
* Make sample project run
* Promote H3 attribute headings to H2
* Add API ref links and 2 new attributes
* Adjust metadata
* Add note about page handler name
* Verbiage tweak
* Another verbiage change
* Fix incorrect template syntax
* Add more complete code snippet
* Improve areas directory structure example
* Remove fully-qualified namespace from Index view
* Replace single quotes with double quotes
* Minor verbiage tweak
* Shorten the Razor Pages code snippets
* Rewording
* Add missing actions to controller
* Word swap
* Adjust rendered link text
* Add working examples
* More code updates
* Fix asp-page sample code
* More verbiage tweaks
* Formatting changes
* Remove custom Tag Helper
* React to feedback
* Fix build error
* Use layout file for Razor Pages
* RP with EF
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* finished with CRUD
* start part 3
* start part 3
* finish Sort/Group
* finish Sort/Group
* finish Sort/Group
* finish Sort/Group
* work
* removed all you
* finished with parts 1-3
* finished with parts 1-3
* finished with parts 1-3
* part 4
* finish mig
* finish mig
* complex
* complex
* complex
* complex
* complex
* react to feedback
* react to feedback
* react to feedback
* react to feedback
* react to feedback
* Added info about calling generic methods to the Razor syntax topic
Info added in the sections on Razor code blocks, implicit expressions, and explicit expressions.
* Made edits suggested by reviewer @guardrex
* Update razor.md
* Update razor.md
* Update razor.md
Addresses #3186
I didn't go with an IntelliSense screenshot because, as you point out,
it's a side note merely highlighting a VS/VSC feature. With the link
there to the IntelliSense topic, I think we're covered.
cc/ @rachelappel
* Create mvc2.md
Added temp file to house doc requested in #3809
* Initial outline of document
* Added Note for Special Tooling (VS 2017 Preview 3)
Will remove when Preview 3 is updated into Release
* Added Porting Link
* Added Core DI Sample
* added DI Section
* Added Storing Configuration Settings Section
* Adding Custom Settings samples
* part of static content
* static content section
* .net standard section
* Adding Edit in VS 2017 Image
* Samples for Startup
* startup and csproj section
* update image reference
* Updates to Migration Doc
changes per @scottaddie
* Final round of changes
Please review
* Edits
* Fix invalid xref link
* More edits
* More edits
* More edits
* More edits
* More edits
* More edits
* Move Content to different directory
* Update Code Sample Links
* change sample location
* ::
* Update Sample Filenames
* Minor edit
* Remove extra space
* More edits
* Move Static Folder
* update reference to image
* Update mvc2.md
* Minor tweaks
* Changes to sample file
* Change copy for Configuration Section
* Fix code formatting
* Remove extra line feed
* Remove extra line feed
* Fix 3xx/4xx/5xx Status Codes in aspnetcore folder
* Take out locality references in urls:
* change MSDN urls to docs.microsoft if possible
* Update aspnet-core-module.md
* Update iis.md
* Remove localization from external links
* Update Docs/aspnetcore/mvc/views/overview.md
Changes to section on View Discovery: 1) Escape angle brackets causing issue with HTML rendering of this section. 2) Clarify and expound upon View(string viewName) behavior.
* Updated per gaurdrex's suggestions
Escaped angle brackets with \<> rather than encoding with <>
* Change for pull #4226 for better styling
Changes made per guardrex's recommendations to better conform to the styleguide.
* What's in a scaffoled Razor Page?
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* work
* Add missing hyphen
* Change code snippet types to cshtml