{"id":5593,"date":"2016-04-05T16:00:29","date_gmt":"2016-04-05T16:00:29","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/dotnet\/?p=5593"},"modified":"2021-09-30T12:03:49","modified_gmt":"2021-09-30T19:03:49","slug":"the-week-in-net-452016","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/the-week-in-net-452016\/","title":{"rendered":"The week in .NET – 4\/5\/2016"},"content":{"rendered":"

To read last week’s post, see The week in .NET \u2013 3\/29\/2016<\/a>.<\/p>\n

On.NET<\/h2>\n

Last week was a thrilling one for the .NET community, with lots of exciting announcements made at the Build conference<\/a>. We decided to move the show to avoid being in direct competition with Build’s live stream. On Monday, we recorded a show with John Kemnetz on the new experimental support for C# debugging in VS Code<\/a>. We tried something a little different this time: instead of our usual one hour discussion, we did a short 20 minute live screencast. Let us know what you think in the comments. This week, Beth Massi and Maria Naggaga are taking over the show<\/a>.<\/p>\n

Package of the week: Autofac<\/h2>\n

With dependency injection baked right into ASP.NET Core, it’s more important than ever to master this technique that can reduce coupling in your applications. ASP.NET provides a minimal container, but is also open for optional replacement containers. Autofac<\/a> is a popular IoC<\/a> container that is now compatible with .NET Core<\/a>.<\/p>\n

The following code shows how you’d register an implementation of an IOutput<\/code> interface from the initialization phase of your application, so that it can later be resolved from other components.<\/p>\n