The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

'WireBase.WireBase(IScheduler)' is obsolete

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

'WireBase.WireBase(IScheduler)' is obsolete

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

'WireBase.WireBase(IScheduler)' is obsolete

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

'WireBase.WireBase(IScheduler)' is obsolete

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

'WireBase.WireBase(IScheduler)' is obsolete

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'WireBase.WireBase(IScheduler)' is obsolete

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

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.

'WireBase.WireBase(IScheduler)' is obsolete

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used

'RdCall<int, string>.Set(Func<Lifetime, int, RdTask<string>>, IScheduler?, IScheduler?)' is obsolete: 'This is an internal API. It is preferable to use SetSync or SetAsync extension methods'

The variable 'entity_id' is assigned but its value is never used