A Brief Look at the .NET Portability Analyzer

Download this episode

Download Video

Download captions

Download Captions


.NET is going through some monumental changes! It is often difficult to even begin to think about how to port our particular code to the various flavors of .NET. In this video Taylor Southwick and Connie Yau spend some time discussing a great tool that will definitely help in this difficult process. I was impressed with how easy it was to ascertain trouble spots that might cause issues when attempting to port libraries over to a more lightweight portable profile. Would love your comments!





Available formats for this video:

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

    The Discussion

    • User profile image

      will the ApiPort (.NET Portability Analyzer: https://github.com/Microsoft/dotnet-apiport) be included in the cli, or be exposed as a tool/command we can use with the cli? E.g.: dotnet analyze <..>

    • User profile image

      @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).


    • User profile image

      @terrajobst:cool, thx for that tip, interesting to try it out once the tools hit rtm!

    • User profile image

      I'm 30 seconds in, and already excited. Thank you for bringing this tool to market. As a Silverlight and WPF dev, this is critical to understand where my apps need to change, and what sort of work is involved. Of particular interest is UWP for Windows 10 IoT on Raspberry Pi 2, and Xamarin.

    • User profile image

      Great video and tools! So, two questions having now watched the whole thing:

      1. Could this service someday be integrated with Roslyn for providing in-line portability information and suggestions (or even transformations)?
      2. What's the chance that this can be extended to XAML markup? IIRC there have been efforts to suggest SL/WPF => UWP mappings. Since it appears to be very pluggable, would also be great to see mapping suggestions (or transformations) to/from Xamarin Forms.
      3. Is the OSS framework generic enough that it would allow API developers a scaffold to offer insights in portability either between it's own API surface (e.g. between versions), or even between it's API surface and that of another framework?
    • User profile image

      @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!


    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.