Introduced IMapperContext to attach user specific data with to an Obj… #13455
Annotations
10 warnings
|
Json/Fliox.Hub/Remote/WebSockets/ServerWebSocketContext.cs#L94
'SHA1Managed' is obsolete: 'Derived cryptographic types are obsolete. Use the Create method on the base type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0021)
|
|
Json/Fliox.Hub/Remote/WebSockets/ServerWebSocketContext.cs#L94
'SHA1Managed' is obsolete: 'Derived cryptographic types are obsolete. Use the Create method on the base type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0021)
|
|
Json/Fliox.Hub/DB/Cluster/RawSqlResult.cs#L45
Field 'RawSqlResult.rows' is never assigned to, and will always have its default value null
|
|
Json/Fliox.Hub/Client/Tasks/Read.Find.cs#L94
Field 'FindRange<TKey, T>.entities' is never assigned to, and will always have its default value null
|
|
Json/Fliox.Hub.WebRTC/Remote/RtcSocketClientHub.cs#L199
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Json/Fliox.Hub.WebRTC/Remote/RtcServer.cs#L38
The event 'RtcServer.LogNull' is never used
|
|
Json/Fliox.Hub.WebRTC/Remote/RtcSocketClientHub.cs#L199
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Json/Fliox.Hub.WebRTC/Remote/RtcServer.cs#L38
The event 'RtcServer.LogNull' is never used
|
|
Json/Fliox.Hub/DB/Cluster/RawSqlResult.cs#L45
Field 'RawSqlResult.rows' is never assigned to, and will always have its default value null
|
|
Json/Fliox.Hub/Client/Tasks/Read.Find.cs#L94
Field 'FindRange<TKey, T>.entities' is never assigned to, and will always have its default value null
|
The logs for this run have expired and are no longer available.
Loading