* Add troubleshooting page for SignalR
* header
* Apply suggestions from code review
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* some fb
* Apply suggestions from code review
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* fb
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* now topic about troubleshooting
According to [this github issue](https://github.com/dotnet/AspNetCore.Docs/issues/19570), I'd like to submit this troubleshooting guidance for common Signalr WebSocket handshake issues.
* Update javascript-client.md
* Update javascript-client.md
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
* Update SignalR JavaScript Client to 3.1
* Full-topic monikers for "< aspnetcore-3.0"
* Full-topic monikers for ">= aspnetcore-3.0" (1 of 2)
* Full-topic monikers for ">= aspnetcore-3.0" (2 of 2)
* dotnet new webapp --no-https
* Cleanup and simplification of templated code/files
* SignalR Hub, CORS, and CDN + snippets
* UI + ES2015
* A few tweaks
* A few more updates
* Update javascript-client.md
Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
Fixing range for `Connect to a hub` section sample code.
Current code shows this:
```js
const connection = new signalR.HubConnectionBuilder()
.withUrl("/chatHub")
.configureLogging(signalR.LogLevel.Information)
.build();
start();
/* this is here to show an alternative to start, with a then
```
New should show this:
```js
const connection = new signalR.HubConnectionBuilder()
.withUrl("/chatHub")
.configureLogging(signalR.LogLevel.Information)
.build();
async function start() {
try {
await connection.start();
console.log("connected");
} catch (err) {
console.log(err);
setTimeout(() => start(), 5000);
}
};
connection.onclose(async () => {
await start();
});
// Start the connection.
start();
/* this is here to show an alternative to start, with a then
connection.start().then(() => console.log("connected"));
*/
/* this is here to show another alternative to start, with a catch
connection.start().catch(err => console.error(err));
*/
```
* Some clarifications to calling server methods in SignalR
* Apply suggestions from code review
Co-Authored-By: anurse <andrew@stanton-nurse.com>
* Add clarifications to .net client doc as well
* Update date on .NET client doc
* Update date on JS client doc
* Apply suggestions from code review
Co-Authored-By: anurse <andrew@stanton-nurse.com>
* 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
Rick Anderson
Scott Addie
Brennan
Dina Berry
FredHan001
Kirk Larkin
Luke Latham
Luke Latham
Ben Randall
Scott Addie
uteschj
Theano Petersen
Mikael Mengistu
Stephen Halter
Andrew Stanton-Nurse
Anthony Chu
Tom Dykstra
Brady Gaster
Corné Hogerheijde
Rachel Appel
Rick Anderson