Immo Landwerth

Program Manager, .NET

Immo Landwerth is a program manager on the .NET Framework team at Microsoft. He specializes in API design, the base class libraries (BCL), and .NET Standard. He works on base class libraries which represents the core types of the .NET platform, such as string and int but also includes collections and IO. He's involved with portable class libraries and works on shipping more framework components in an out-of-band fashion via NuGet.

Post by this author

Announcing .NET Standard 2.0

The .NET Standard 2.0 specification is now complete. It is supported in .NET Core 2.0, in the .NET Framework 4.6.1 and later versions, and in Visual Studio 15.3. You can start using .NET Standard 2.0 today. While this post demos .NET Standard in C#, it's also supported in Visual Basic and F#. For more details, take a look at the .NET ...

Introducing Support for Brotli Compression

This post was written by our software developer intern Denys Tsomenko, who worked on a Brotli compression library during his internship. Modern web-pages are getting larger and larger with huge CSS, HTML and JavaScript files. But the Internet connection isn't always good and pages can load slowly. Web pages also often contain other ...

.NET Fringe: A Great Role Model for Community Oriented Conferences

A few of us just went to a smaller .NET conference in Portland, called .NET Fringe. For me, it was the third time I attended .NET Fringe. I've realized that this conference has gained a special place in my heart, so thought it would be worthwhile writing up why that is. My goal isn't to convince you to attend .NET Fringe per se, but to ...

Introducing .NET Standard

Questions? Check out the .NET Standard FAQ. You can find the latest version of the compatibility matrix here. In my last post, I talked about how we want to make porting to .NET Core easier. In this post, I'll focus on how we're making this plan a reality with .NET Standard. We'll cover which APIs we plan to include, how cross-framework ...

.NET Support and Versioning

This post was written by Lee Coward. We’ve travelled many new roads in the process of releasing .NET Core 1.0, ASP.NET Core 1.0 and Entity Framework Core 1.0. Developing the projects in the open and delivering to Mac and Linux have been exciting experiences and the feedback we continue to receive shows that the excitement is shared by many...

.NET Core Roadmap

This post was written by Scott Hunter. It has been about two weeks since we shipped .NET Core / ASP.NET Core 1.0. The team has used the past two weeks to take a deep breath, and is now getting started on planning what is coming next. We have seen a lot of .NET Core SDK downloads and significant feedback. Please keep the feedback coming. Here...

Making it easier to port to .NET Core

In my last post, I talked about porting to .NET Core and requested feedback from our community on what their experience was and what we could improve. This sparked many great conversations with our users. Based on these conversations as well as our experience working with first- and third-party partners, we've decided to drastically simplify...

.NET Framework Compatibility Diagnostics

This post was written by Taylor Southwick, a software engineer on the .NET team. Introduction Updates to the .NET Framework 4 are delivered as highly-compatible in-place updates, which helps keep users' applications running on the latest and most secure versions of the .NET Framework. Some deviation from previous behavior has beeen seen when ...

Porting MSBuild to .NET Core

This post was written by Daniel Plaisted, a software engineer on the .NET Team. It's an exciting time for .NET. With .NET Core, we're moving full speed ahead into an open source, cross-platform world. .NET Core provides a framework for your apps that is modern, app-local, cross-platform, and open source all the way down. However, .NET Core ...

Porting to .NET Core

.NET Core is getting closer and closer to an RTM release. Only two months ago, we announced the RC release of .NET Core and ASP.NET Core. As part of our validation, we're working with internal as well as external customers to port their code to .NET Core. We received many requests from you asking us how you should go about migrating ...