61 | {JSON.stringify(message, null, 2)} 62 |63 | ); 64 | 65 | return ( 66 |
27 | Edit 28 |
29 |18 | Connected to entity framework through signalr 19 |
20 |26 | Disconnected 27 |
28 |34 | Waiting for connectionId 35 |
36 |42 | Connecting to entity framework through signalr 43 |
44 |{{message}}76 | 77 |
{{filterMessages}}83 | 84 |
{{joke}}90 | 91 |
{{joke}}97 | 98 |
Make all of your data real time. Receive updates no matter where the object was created or edited! Uses existing ASP.NET core permissions system.
13 |
14 |
15 |
17 | View On GitHub 18 |
19 |30 | Entity Signal allows you 31 | to connect to Entity Framework through SignalR and get updates on subscribed data in real time. This lowers the number 32 | of refreshes done by the user and ultimately allows you to do more with fewer servers. It is also requires minimal changes, 33 | so you can make real-time apps about as easily as you can make standard apps. 34 |
35 |
42 | Sync Frontend Collection To Backend Entity signal will make sure that a given collection will remain in sync with the backend
43 |
44 | Second Query Instant Requesting the same endpoint 2 times? The second request is returned instantly if the first is already synced.
45 |
46 | Performance Entity signal allows you to do more with less, while also delivering realtime functionality
47 |
48 | Stable and Scaleable Foundation Built inbetween entity framework and signalr entity signal is built on a stable and scaleable foundation
49 |
50 |
57 | VanillaJs (Quick Start Guide)
58 |
59 | React (Example) (Integration Guide)
60 |
61 | VueJs (Example) (Integration Guide)
62 |
63 | AngularJs (Example) (Integration Guide)
64 |
65 | .Net Standard (Integration Guide)
66 |
67 | Xamarin (Integration Guide)
68 |
77 |Clever solution from @@dustout called EntitySignal that bridges .NET's Entity Framework and ASPNET Core's SignalR's realtime websocket notifications https://t.co/D9UXUFbLXh
— Scott Hanselman (@@shanselman) May 14, 2019
80 |Amazing!! It’s remember me Firebase real-time
— Alexsandro (@@alexsandro_xpt) May 16, 2019
Tracked Users (entity signal): @connectedUsers.Count()
12 |
12 | Request ID: @Model.RequestId
13 |
18 | Swapping to Development environment will display more detailed information about the error that occurred. 19 |
20 |21 | The Development environment shouldn't be enabled for deployed applications. 22 | It can result in displaying sensitive information from exceptions to end users. 23 | For local debugging, enable the Development environment by setting the ASPNETCORE_ENVIRONMENT environment variable to Development 24 | and restarting the app. 25 |
26 | -------------------------------------------------------------------------------- /EntitySignal/Views/Shared/_AngularJs.cshtml: -------------------------------------------------------------------------------- 1 | 8 | Connected to entity framework through SignalR 9 |
10 |16 | Disconnected 17 |
18 |24 | Waiting for connectionId 25 |
26 |32 | Connecting to entity framework through SignalR 33 |
34 |_entitySignal.Subscribe<Message>();
65 | {{message | json}}67 | 68 |
_entitySignal.Subscribe<Message>(x=>x.Id % 2 == 1);
73 | {{filterMessages | json}}75 | 76 |
_entitySignal.Subscribe<Joke>();
81 | {{joke | json}}83 | 84 |
_entitySignal.Subscribe<Joke>(x => Guid.TryParse(x.Punchline, out Guid g));
89 | {{joke | json}}91 | 92 |
71 | {JSON.stringify(message, null, 2)} 72 |73 | ); 74 | return ( 75 |
155 | Connected to entity framework through signalr 156 |
157 |164 | Disconnected 165 |
166 |173 | Waiting for connectionId 174 |
175 |182 | Connecting to entity framework through signalr 183 |
184 |