* initial commit
* refactored
* forgot the content
* formatting
* updated title
* Updated outline, wrote intro
* added list
* changes for feedback
* added list
* review time
* Fixed image paths
* Wade's feedback
* Typo
* clarity and polish
* clarity and polish (#6517)
* UE pass on Chapter 3 (#6533)
* Saving notes for DevOps pipeline creation (#6539)
Added some rough notes outlining much of the DevOps creation setup
* Prepare Azure Lifecycle Chapter 2 for Chapter 4 writing (#6536)
* Add notes for building build and release definitions in VSTS
* More work on VSTS release definition steps
* Refine Azure lifecycle CI/CD setup instructions (#6601)
Simplify the instructions by creating VSTS artifacts via **Continuous Delivery (Preview)** option in the Azure portal.
* Add screenshots to Azure lifecycle DevOps chapter (#6606)
* Add screenshots to Azure lifecycle DevOps chapter
* Minor tweaks
* Explain the VSTS release definition (#6608)
* Add screenshots to Azure lifecycle DevOps chapter
* Minor tweaks
* Explain release definition
* merging
* New troubleshooting doc and more
* New troubleshooting doc and more (#6718)
* clarity and polish
* merging
* New troubleshooting doc and more
* border images
* image borders
* Image fixes (#6720)
* clarity and polish
* merging
* New troubleshooting doc and more
* border images
* image borders
* edit pass
* moar edits
* links
* fixed image
* a word
* fixed another link
* fixed formatting
* more AI
* Add instructions for locating resources in Azure portal (#6787)
Also incorporate Acrolinx suggestions
* Add more screenshots for CD steps (#6789)
* Explain build definition in Azure Lifecycle Ch. 4 (#6794)
* Add content for triggering build and deploy via a GitHub push (#6797)
* no idea but I need to merge upstream
* Azure lifecycle (#6798)
* clarity and polish
* merging
* New troubleshooting doc and more
* border images
* image borders
* edit pass
* moar edits
* links
* fixed image
* a word
* fixed another link
* fixed formatting
* more AI
* no idea but I need to merge upstream
* Escape special characters in DevOps chapter (#6856)
* UE edit of Azure lifecycle Chapter 5 (#6859)
* UE edit of Azure lifecycle Chapter 5
* Minor tweak
* Add new instructions for DevOps pipeline creation (#7033)
* ready for review!
* revisions
* Experimenting with positioning
* ASP.NET site changes
* headings
* wording
* wrong directory - whoops :)
* cleaning up for no confusion
* toc experiments
* removing numbers from filenames
* refactoring directories and paths
* refactoring directories and paths
* metadata update for docfx
* Modify metadata
* Add metadata
* Add metadata
* Delete empty line
* Edit uid
* Add metadata
* Add metadata
* Add metadata
* Edit ToC title and xref link
* Convert to xref links
* Remove placeholder section
* Minor tweaks
* Convert to xref links
* Minor tweaks
* repo --> repository
* Acrolinx pass
* Acrolinx pass
* Acrolinx pass
* Acrolinx pass
* acknowledgments
* Convert to xref link
* Remove gerund
* rearrange TOC
* case
* Unit testing notes, DevOps updates for UI changes
* Added cover, converted to docx
* fixed typo
* removed extra file
* removing docx
Somehow some of the SignalR docs got moved to the "Client-side development" hive. This should move them back, if I understand how the TOC file works properly :)
When creating a new PR, please do the following and delete this template text:
* Reference the issue number if there is one:
Fixes #Issue_Number
> The "Fixes #nnn" syntax in the PR description causes
> GitHub to automatically close the issue when this PR is merged.
Hello, @scottcate,
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
"There's an extra asterisk that's breaking the Note code. In case the italics must be conserved, we suggest to start them on line 53."
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.
* Expanding out HSTS values
Add a line explaining once you're confident in HSTS you should increase the value from the default, and expanding out the click through prevention.
* Touch-ups
Had a question about default values for the config values and I figured it would be faster to answer by updating the docs ;).
Not committed to the formatting. I thought a new column could work well but I could also do this as sentences in the Description column (some of the options already had this, I think I moved them all)
[Internal Review Page](https://review.docs.microsoft.com/en-us/aspnet/core/signalr/configuration?view=aspnetcore-2.1&branch=pr-en-us-7906)