Sean Feldman
Sean Feldman
@nemakam `help wanted` - wouldn't that need to wait or can it be done on `develop`?
I'm asking because asking for help when it's not the time will cause PR hang out there and become outdated, causing unnecessary friction as a result of conflicts with other...
Could really use this feature for what doing now.
The default logging level is set to `Warning` `Azure.Core` is set to `Error`. Microsoft.Azure.Functions.Worker version 1.6.0 Function Runtime Version: 4.3.2.18186 And yet I get a flood of these: ``` [2022-06-02T18:33:14.917Z]...
@mikeminutillo so despite overriding the component registration from a custom feature by calling ``` context.Container.ConfigureComponent(_ => new BsonDataBusSerializer(), DependencyLifecycle.SingleInstance); ``` The `DefaultDataBusSerializer` is not replaced. Is there a way to...
So in the case of Azure Functions, it's a bit more complicated than just `IServiceCollection`. NSB adapts a type that is already an adapter for Functions. I don't see any...
Ironically, it appears that Functions also has an issue with this. The only way to address it is to remove the default `IDataBusSerializer` found in the `IServiceCollection` passed into the...
I'd like to bring attention to this year-old issue. With .NET 6 that is what anyone on .NET Core is going to use from now on, `BinaryFormatter` is not an...
FWIW, delayed or in-flight messages with attachments will require some sort migration process/tooling.
[This](https://weblogs.asp.net/sfeldman/fixing-nservicebus-default-databus-serializer-in-net-6) was my workaround for this issue.