Historically, the Dapr clients have configured options via values pulled independently from environment variables - this PR instead prioritizes pulling from arguments, IConfiguration and then from environment variables.

While a previous PR provided a detailed explainer on Data Contract serialization in the context of strongly-typed actor clients, this supplemented that work with an explainer on JSON serialization provided by System.Text.Json in both strongly- and weakly-typed actor clients

Removes all Dapr protos out from their separate projects to a shared Dapr.Protos project as part of broader refactoring

Removes several shared classes imported by project file reference to a shared Dapr.Common project as part of broader refactoring

The upcoming release of .NET 9 adds greater vulnerability awareness through NuGet to direct and transitive package refernces. This is an early effort to apply all known CVEs, use central package management and update packages to their latest .NET 6 compatible versions

As the Workflow block is approaching stable status, this effort removed obsolete methods from the Dapr.Client project and refactored an erroneously placed type

Added unit test to validate additional scenario in Secrets API

Added unit test to validate headers passed in service invocation request are preserved by sender

Added fix to better handle null values returned from the Metadata API

Added missing branch to switch statement to fix bug

Added support for the missing EventHubBufferedProducerClient in addition to the existing EventHubProducerClient and EventHubConsumerClient in Aspire's Event Hub implementation.

Two environment variables I was recently working in another contribution were missing from the reference documentation, so this PR added them.

This PR adds an overload to the service invocation functionality in Dapr by explicitly allowing key/value pairs to be appended to the invocation URL

This PR adds access to an instance of IServiceProvider in the registration method for the Dapr client enabling developers to access values from the configuration or other registered services during the Dapr client registration.

This PR adds support for Azure Batch as a deployment target for the project.

The documentation described different workflow patterns, including a fan-out/fan-in pattern. But it ended with a note suggesting how to take the idea further, but without elaborating. This PR contributes a code sample providing precisely that elaboration.

When a certain well-known environment variable was being set with the expectation that it'd be used for tracing, the Dapr runtime wouldn't recognize it. In this PR, it not only recognizes, but prioritizes it over configured values when set.

An issue was raised indicating that a method was returning a null value despite not being marked with the appropriate annotations. This provides those annotations to this method.

With the release of .NET 8, the best practice guidance shifted from use of the app.UseEndpoints method and instead to registration directly on the app instance. This PR updated such guidance in the Dapr documentation.

The introduction of the Auto rendermode in the .NET 8 version of Blazor broke any implementation of Fluxor that utilized it as the state would be lost during any transition from Server to WASM. This PR added a pluggable state persistence layer that restored project compatibility.

When a resource was defined, it would produce an invalid value name for the template resource name argument. This PR corrected the issue here and across all dependencies of the value.

This PR added support for high-performance and bidirectional streaming of data for encryption and decryption of strings or streams compatible with .NET 6 and newer.

Seeking to complement the Cryptography support provided for the .NET Dapr client in another PR, this PR updates the documentation with descriptions and reference information regarding the functionality.

This PR added explicit samples demonstrating encryption and decryption operations with the .NET Dapr client

There have been many versions of C# released since the DataContract serialization library was originally introduced. As such, there's been some confusion around how serialization should behave using more modern C# functionality. This article performs a deep-dive analysis with examples into how newer C# capabilities can be readily used.

Prior to this PR, data retrieved via a call to GetBulkStateAsync would simply returned as a string. This PR instead deserializes the data to the generic type specified using the serialization engine configured with the Dapr client.

A bug report was filed indicated something wasn't working as intended. I created a unit test to prove that the client was handling the operation as expected

The Dapr documentation cited a bad link in the Azure App Configuration documentation describing authentication with Azure. This PR corrected this link with an appropriate URL.

Newer versions of Azure Service Fabric use new serialization settings. This PR adds overloads to a set of extensions that ship with the Service Fabric .NET SDK to support exception serialization using a custom IExceptionConverter for V2 remoting purposes.

This PR comprised an example project demonstrating how to add aspects to multiple projects using Metalama Fabrics.

Fixed an issue that prevented scaling in the web explorer interface due to a badly formed regular expression.

In the web explorer interface, clicking the timestamp header to change the sort order didn't do anything, and this fixed PR this experience.

If more than ten colors were placed in the legend, the remaining elements wouldn't have a fill color. This fix changed this behavior so the colors would just repeat.