-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call ConfigureAwait(false) on all library related await calls #2500
Conversation
All commits are 1 per solution (except the fixing one, which the analyzer couldn't figure out correctly) |
That's a great contribution. Thank you for your huge effort. |
@mehmetuken mentioned a https://github.com/Fody/ConfigureAwait class library. It can save a lot of code. I haven't tried it, but from the introduction, it really is. |
@maliming adding Fody to the build pipeline might be painful... when it works, it works fine: when it doesn't, you'll want to pull all your hairs off... I'd GREATLY recommend AGAINST it for a library. I find it more than ok for app code (I've used it in the past for many things), but not for a library :-) |
@maliming Fody seems good, yes, but I also think to not add a new dependency for now. I will merge this PR and delay the Fody decision. |
Related to #2497
Only added the
ConfigureAwait(false)
calls on library solutions (all Volo.Abp.* solutions).All tests pass except for 1 but doesn't seem related to this. The failing one is:
Volo.Abp.Emailing.EmailTemplateStore_Tests.Should_Get_Registered_Template_With_Layout
Which fails with:
Doesn't seem related to any of these commits and should probably be fixed separately