* Fill in SDK gaps
* Apply suggestions from code review
Co-Authored-By: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Update web-sdk.md (#16703)
* Update web-sdk.md
* Update web-sdk.md
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Update ui-class.md
Fixes#14946
Updated VS instructions for new project to VS 2019. Tested CLI new project instructions, they are good as is.
* Update ui-class.md
Removed repeated lines.
* Update ui-class.md
Made corrections per rick-anderson review. Thanks Rick.
* Update ui-class.md
Corrected new project > select support pages instruction line to so it makes more sense for the 3.0 specific content within the context of its >= 3.0 moniker range.
Removed unneeded metadata moniker line. The original had mixed metadata and inline range monikers, so corrected.
Updated reference to customer model in the Validation section to the following reference: [!code-cs[](index/3.0sample/RazorPagesContacts/Models/Customer.cs)]. Customer model in "Write a basic form" section and the "Validation" section will reference the same code.
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
Description: Missing break-line before snippet is preventing content to show properly.
* 3.0 update: intro to RP
* 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
* Update aspnetcore/razor-pages/index.md
Co-Authored-By: Ryan Nowak <nowakra@gmail.com>
* Document default Content globs for Web and Razor SDKs
* Update aspnetcore/host-and-deploy/visual-studio-publish-profiles.md
Co-Authored-By: Luke Latham <1622880+guardrex@users.noreply.github.com>
* Update aspnetcore/host-and-deploy/visual-studio-publish-profiles.md
Co-Authored-By: Luke Latham <1622880+guardrex@users.noreply.github.com>
* React to feedback
* Minor edits
Fixes#6801
* Add example code for `IPageHandlerModelConvention` to the sample app (but it's not wired up to do anything really ... just shows how to implement it generally).
* Take sample app to 2.2.
* Drop the *Replace the default page app model provider* and sample code for it per instructions from engineering (see the issue).
* Take topic to 2.1+ (shed 2.0 content).
* XREF links (I really suspect that a VSC Extension could do 90% of the conversion work ... I should consider creating it.)
* Whoops - didn't mean to merge that to this branch!
* minor updates
* minor updates
* Fixed issue #8552
* added a note on URL
* made Auth URL consistent with the portal (rather than Visual Studio)
* added a cool dagger for Luke
* phrasing
* formatting
* formatting - re-adding code fenced URLs
* Update azure-ad-b2c-webapi.md
* SEO 2018 for /core/azure and /core/security directories
* SEO 2018 for /core/razor-pages directory
* added custom tag
* 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.
Fixes#9217
Came to fix versioning ... there was a build warning on another PR.
It looks like the whole topic should be versioned >=2.1, so that's what I did.
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.
* Update ui-class.md
@pranavkm @Rick-Anderson These changes would clarify that multiple file structures can be used and give an example of one alternative.
* Update ui-class.md
* Update ui-class.md
* Update ui-class.md