Immo Landwerth

Back to Profile: terrajobst


  • Getting Started with .NET Standard 2.0 Part 1 with Immo Landwerth

    I wonder where Jon sat ;)

    Hah! He has a strong (tele) presence. He's always around :)


  • Getting Started with .NET Standard 2.0 Part 1 with Immo Landwerth

    Thanks Maria! Normally I don't get accused of being too quiet :)

  • Get started with VS Code using C# and .NET Core on a Mac

    Great video but the papers are highly distracting. Get your office in order! ;)

  • Introduction to .GAME

    Very cool! Keep it going :)

  • What is .NET Standard?

    Am I understanding this right, an Xamarin App will run on windows ( with any needed windows renderers ) on the basis that Xamarin API's are inside .net standard?

    No. Xamarin provides .NET flavors that allow you to run apps on iOS and Android. We don't have any plans to add a UI stack to .NET Standard. UI is a platform specific technology.

    Xamarin Forms is an abstraction over the platform specific UI stacks that allows you to share UIs across different operating systems.

  • What is .NET Standard?

    , raghurana wrote

    I don't fully understand what  "Microsoft.NETCore.Portable.Compatibility" and "NETStandard.Library" are.

    Microsoft.NETCore.Portable.Compatibility is a NuGet package that provides the magic that makes your project compatible with existing Portable Class Libraries (PCL). PCLs were our solution to create class libraries that can be shared across multiple .NET flavors, prior to .NET Standard.

    NETStandard.Library that's the NuGet package that you reference to build a class library targeting .NET Standard 1.x.

  • A Brief Look at the .NET Portability Analyzer

    @dcuccia:Sorry for the delay. I was confused which two of the three questions I should answer (6)

    1. Yes, we're playing around with the idea of provide an analyzer.

    2. That's an interesting suggestion.

    3. Are you asking whether our suggestion engine could be extended to incorporate non-platform libraries? We've talked about this recently and came to the conclusion that it should be possible as our engine used string-based IDs to refer to APIs.

    These are all excellent ideas. I suggest you file issues on GitHub so we can talk about them there in more detail!

  • A Brief Look at the .NET Portability Analyzer

    @LeRenard242: That's a great suggestion!

    I think for now we're trying to keep the dotnet command pristine and avoid letting it become too much of a dumping ground. However, I don't see why this wouldn't work in the future. AFAIK, if API port is named dotnet-analyze and in the path, dotnet analyze should work (similar to how git works).


  • GoingNative 45: Incredi-​builds with IncrediBuild -- free in Visual Studio 2015!

    A Microsoft Program Manager promoting an apple product... interesting...

    Not sure why our usage of MacBooks is considered a big deal. Many of us work on software that is designed to to run on multiple platforms. A MacBook is the most convenient way to run all operating systems we've to support.

    Besides, when I joined five years ago my manager had the cool Apple "Think Different" poster in her office. We may not have always had the broad cross platform offering we have today, but it's certainly not new that we've a quite diverse use of technology and software at Microsoft.



  • The .NET Voyage into Open Source

    @Tarik and @Jojo

    I think you guys interpret way too much into the presence of our MacBooks. First of all, the one I'm using is a backup machine because my actual laptop (a fabulous ThinkPad W530) couldn't project. Why? Because I'm passionate about Windows and I'm generally running the latest builds. As you can imagine, that doesn't always work great with all hardware, especially projectors.

    Secondly, it is true that many devs on our team use MacBooks. It's the easiest way to run all OS we support (Windows, Mac, and Linux).

    Thirdly, Microsoft is an employer that values diversity. When you walk over the campus, you'll find all sorts of hardware (for business as well as personal use). I fail to see how this can possibly be a bad thing. In the end, our customers expect us to support our software in wide variety of scenarios.

  • Introduction to API Reviews

    Smaller size videos please. Thanks.

    Above video is not compressed please make it small.

    Sorry about that. I probably messed up the upload...

    , DanRevell wrote

    What's this book you guys keep referencing?

    Here is the Amazon link.

  • .NET Core API Review 2015-01-14

    , Charles wrote

    Really nice to see this old school approach finally materialize in 2015. We often talked about filming meetings and sharing them on C9, but we never got around to pulling it off (and frankly never figured out how to make it an enjoyable experience for viewers...). 

    Great work, Immo et al! Looking forward to more of these. API reviewing is currently one of the things we do on my not-so-new team. Great learning here!

    Thanks for the kind words! You bet we keep posting :)

    , davewill wrote

    I vote for throwing some code reviews in too.

    We don't do meetings for code reviews as this would be terribly inefficient. For code reviews, our team members use pull requests which you can follow and participate in on GitHub.

    Good video. I would like to see more of this. Thanks.

    Sure thing!

    , Alxandr​Heintz wrote

    What application are you using to view the diffs and add comments.

    See this thread on Twitter.