Alexander Batishchev comments

Results 192 comments of


                                            Alexander Batishchev

Provide option to await all initializers at once, instead of awaiting each separately

I don't think anything from the library itself is needed to achieve this. You can inject `IEnumerable` and then `await Task.WhenAll(initializers)`. No?

Provide option to await all initializers at once, instead of awaiting each separately

Right. It worked for me because I'm using Simple Injector instead of MSDI which allows to register single dependencies separately from collections. So I register real initializers as a collection...

[Feature Request] az pipeline build queue wait for completion

Any update on this, please? It's 2021 already, you know.

Library should include both Json.Net and System.Text.Json serialziers

Yes, I'm thinking if we should include both serialziers into the assembly and the user would have a choice. Tests must be updated to test everything against both serialziers too,...

Library should include both Json.Net and System.Text.Json serialziers

Yes, I was also thinking about a parameterized tests. However it might not work for those which are already parameterized, and iirc there are already few of them. Another option...

Library should include both Json.Net and System.Text.Json serialziers

> Yeah, having subclasses with MSTest is a pain I have experienced it myself firsthand :) Yes :( > Perhaps we can migrate to Xunit for the tests so we...

Library should include both Json.Net and System.Text.Json serialziers

Ping on this idea.

Library should include both Json.Net and System.Text.Json serialziers

tbh, I don't remember what was the exact trigger. I always liked MSTest but back then it didn't support dynamic test data, xUnit did so I've switched. But then MSTest...

Split NuGet package into few child packages to ease dependencies

Sounds like a plan! I would just avoid calling it Core to avoid confusion with .NET Core. At work I usually call such project Contracts but we can make up...

Split NuGet package into few child packages to ease dependencies

Yes, I think that would be the right time to do it.