You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update Actions to use dotnet build (#1663)
* Update windows.yml
* Add configurable options (#1654)
* Update CI to enable net7.0 preview builds (#1677)
* Support net7.0
* update osx/ubuntu.
* revert common package upgrade.
* update build-source guide and revert net7.0 in src.
* Add OrTimeout()
* Fix build warnings and add net6 samples (#1676)
* Fix build warning
* Update docs
* Fix build failure
* Fix test failure
* Fix vlunerability issue (#1678)
* Fix vlunerability issue
* fix filters
* fix filters
* Update use-signalr-service.md (#1683)
* Change emulator to net6.0 (#1682)
* Change emulator to net6.0
* Fix test
* Add filter property...... (#1686)
* Add filter
* Add multiPayload case
* Adding comments
* Update management-sdk-guide.md (#1689)
Improve a confusing statement. The original statement can also be interpreted as this SDK only supports SignalR clients based on ASP.NET Core C#, which confuses users. #1688
* Expose InstanceId in ClientConnectionContext (#1692)
* Fix `HubConnectionContext.UserIdentifier` is null when negotiation with Management SDK (#1691)
When clients negotiatie with Management SDK and connect to SignalR server, IUserIdProvider might not work as the user ID is set directly in the Management SDK.
To make HubConnectionContext.UserIdentifier have the valid value in this case, we should set it before the server accesses it. HubLifetimeManager{THub}.OnConnectedAsync(HubConnectionContext) is the only chance we can set the value. However, we cannot access the Constants.ClaimType.UserId as ASRS system claims are trimmed there. HubConnectionContext.Features is the place where we can store the user Id.
The following code is the injection point.
https://github.com/dotnet/aspnetcore/blob/v6.0.9/src/SignalR/server/Core/src/HubConnectionHandler.cs#L132-L141Fixes#1679
* Add ClientInvocationManager (#1684)
* add ClientInvocationManager
* update CallerClientResultsManager (#1697)
add `TryCompleteResult` for `ErrorCompletionMessage`
* Implement close on client authentication expiration (#1699)
* Add spec for client-invocation. (#1701)
* Add spec for client-invocation.
* minor update direction for ErrorCompletionMessage
* Add client Invocation implementation and UTs (#1687)
* Add client Invocation implementation and UTs
* [ClientInvocation] Fix cleanup in caller case. (#1702)
* Fix cleanup in caller case.
* fix UT.
* Update src/Microsoft.Azure.SignalR.Common/ClientInvocation/IClientInvocationManager.cs
Co-authored-by: Liangying.Wei <[email protected]>
Co-authored-by: Liangying.Wei <[email protected]>
* Add ClientResultSample (#1703)
* Add ClientResultSample
* Move file
* minor update.
* minor update README.
* show server/service ex.message
* Add Broadcast method and update README
* Fix proxy not applied to serverless transient mode (#1708)
Fix#1700
* silent IDE0090 check (#1709)
* reduce retry interval when auth failed (#1451)
* Clean up dependencies. (#1711)
* Update dep to GA version.
* clean up dependencies
* clean management.
* fix test dep.
Co-authored-by: Liangying.Wei <[email protected]>
Co-authored-by: Kevin Guo <[email protected]>
Co-authored-by: yzt <[email protected]>
Co-authored-by: Eric Xing <[email protected]>
Co-authored-by: Terence Fan <[email protected]>
You can build the entire project on command line with the `build.cmd`/`.sh` scripts.
28
+
You can build the entire project on command line with the [`dotnet` command](https://docs.microsoft.com/dotnet/core/tools/dotnet). Run command below in the repo's root folder.
29
29
30
-
On Windows:
31
30
```
32
-
.\build.cmd
33
-
```
34
-
35
-
On macOS/Linux:
36
-
```
37
-
./build.sh
31
+
dotnet build
38
32
```
39
33
40
34
## Building in Visual Studio
41
35
42
-
Before opening our .sln files in Visual Studio or VS Code, it is suggested to run `.\build.cmd` to make sure all the dependencies are restored correctly.
43
-
44
-
The solution file is **AzureSignalR.sln** in the root.
45
-
46
-
## Build properties
47
-
48
-
Additional properties can be added as an argument in the form `/property:$name=$value`, or `/p:$name=$value` for short. For example:
49
-
```
50
-
.\build.cmd /p:Configuration=Release
51
-
```
52
-
53
-
Common properties include:
36
+
Before opening our .sln files in Visual Studio or VS Code, it is suggested to run `dotnet restore` to make sure all the dependencies are restored correctly.
Copy file name to clipboardExpand all lines: docs/management-sdk-guide.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
# Azure SignalR Service Management SDK
2
2
3
-
> **NOTE**
4
-
>
5
-
> Azure SignalR Service only supports this SDK for ASP.NET CORE SignalR clients.
3
+
This SDK is for ASP.NET **Core** SignalR. For differences between ASP.NET SignalR and ASP.NET Core SignalR, see [here](https://learn.microsoft.com/aspnet/core/signalr/version-differences?view=aspnetcore-6.0).
6
4
7
5
## Build Status
8
6
@@ -190,4 +188,4 @@ This SDK can communicates to Azure SignalR Service with two transport types:
190
188
191
189
192
190
### Next steps
193
-
*[Customizing Json Serialization in Management SDK](./advanced-topics/json-object-serializer.md)
191
+
*[Customizing Json Serialization in Management SDK](./advanced-topics/json-object-serializer.md)
0 commit comments