Creating Async Libraries That Are Modular, Reusable and Fast, in Microsoft Visual C# and Visual Basic

Download this episode

Download Video

Description

We all try to make our code modular and reusable. But when it comes to reusable async code there are some special concerns and best-practices. The code shouldn’t lie—if its name and signature are async, then it shouldn’t block or use CPU resources. The code should be agnostic about its threading environment, and usually needs ConfigureAwait to achieve this. The code might be used from perf-sensitive code, and there are some handy ways to optimize the common case. These principles evolved into internal guidance at Microsoft for how we developed the Microsoft .NET Framework 4.5. In this session, learn our guidance, and leave knowing how to apply it to your own projects.

Tag:

Breakout

Day:

3

Level:

400 - Expert

Session Type:

Breakout

Code:

DEV-B318

Room:

Hall 4.4

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.