{"id":20632,"date":"2018-08-08T10:00:25","date_gmt":"2018-08-08T17:00:25","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/dotnet\/?p=18635"},"modified":"2019-09-11T18:18:56","modified_gmt":"2019-09-12T01:18:56","slug":"are-your-windows-forms-and-wpf-applications-ready-for-net-core-3-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/are-your-windows-forms-and-wpf-applications-ready-for-net-core-3-0\/","title":{"rendered":"Are your Windows Forms and WPF applications ready for .NET Core 3.0?"},"content":{"rendered":"

\"Download\"<\/a> Download Portability Analyzer<\/strong><\/a> (2.37 MB)<\/strong><\/p>\n

At Build 2018 we\u00a0announced<\/a>\u00a0that we are enabling Windows desktop applications (Windows Forms and Windows Presentation Framework (WPF)) with .NET Core 3.0. You will be able to run new and existing Windows desktop applications on .NET Core and enjoy all the benefits that .NET Core has to offer, such as application-local deployment and improved performance.<\/p>\n

We want to make sure that .NET Core 3.0 includes all the APIs that your applications depend on. So, in order to learn about which APIs are being used, we are releasing Portability Analyzer that will report the set of APIs referenced in your apps that are not yet available in NET Core 3.0. This API list will be sent to Microsoft and will help us prioritize which APIs we should incorporate to the product before it ships.<\/p>\n

Please\u00a0download<\/a>\u00a0and run the tool (PortabilityAnalyzer.exe<\/em>) on your Windows Forms and WPF apps to see how ready your apps are for .NET Core 3.0 and to help us shape the .NET Core 3.0 API set.<\/p>\n

<\/a>The Portability Analyzer<\/h2>\n

The Portability Analyzer is an\u00a0open source tool<\/a>\u00a0that simplifies your porting experience by identifying APIs that are not portable among the various .NET Platforms. This tool has existed for a few years as a\u00a0console application<\/a> and a\u00a0Visual Studio extension<\/a>. We recently updated it with a Windows Forms UI, which you can find here<\/a>. You can see what it looks like in the following image.<\/p>\n

\"\"<\/a><\/p>\n

Running the tool will do two things:<\/p>\n

    \n
  1. Generate an Excel spreadsheet that will report the level of compatibility that your project has with .NET Core 3.0, including the specific APIs that are currently unsupported.<\/li>\n
  2. Send this same data to the .NET team at Microsoft so that we can determine which APIs are needed by the most people.<\/li>\n<\/ol>\n

    The data we are collecting is the same as what is in the spreadsheet. None of your source code or binaries will be sent from your machine to Microsoft.<\/p>\n

    In order for us to know which APIs our users need, we are asking you to run the tool which will help us to provide the best possible experience in porting your apps. You, at the same time, will see how portable your apps are right now since the tool generates a list of APIs referenced in your assemblies, that might not be supported in .NET Core 3.0.<\/p>\n

    We will prioritize adding new APIs in .NET Core 3.0 based on information we collect. Please help us help you by making sure your application\u2019s API requirements are represented in the data that we use for prioritization. Please run the Portability Analyzer to ensure that your application is counted.<\/p>\n

    <\/a>Using Portability Analyzer<\/h2>\n

    Use the following instructions to run Portability Analyzer.<\/p>\n

      \n
    1. Extract archive anywhere on your local disk.<\/li>\n
    2. Run\u00a0PortabilityAnalyzer.exe<\/em><\/li>\n
    3. In the\u00a0Path to application<\/strong>\u00a0text box enter the directory path to your Windows Forms or WPF app (either by inserting a path string or clicking on\u00a0Browse<\/strong>\u00a0button and navigating to the folder).<\/li>\n
    4. Click\u00a0Analyze<\/strong>\u00a0button.<\/li>\n
    5. After the analysis is complete, a report of how portable your app is right now to .NET Core 3.0 will be saved to your disc. You can open it in Excel by clicking\u00a0Open Report<\/strong>\u00a0button.<\/li>\n<\/ol>\n

      Below is an example of the report you’re getting after running the tool for the popular Paint.NET application:<\/p>\n

      \"\"<\/a><\/p>\n

      Note:<\/strong> In your report you might have a tab “Missing Assemblies”. It means that the analyzer could not find the source assemblies that are referenced in your application. Make sure to find those assemblies and add them to the folder you’re analyzing. Otherwise you won’t get the full picture of your application.<\/em><\/p>\n

      Troubleshooting<\/h3>\n

      Currently Portability Analyzer cannot analyze resource assemblies (*..resources.dll<\/em>). This results in the error message:<\/p>\n

      Unable to analyze.<\/em>\nDetails:<\/em>\nDetecting assembly references [Failed]<\/em><\/p>\n

      Cannot locate assembly information for System.Object. Microsoft assemblies found are:<\/em><\/p>\n

      We are working on providing a fix. To unblock analysis until the fix is available, you can remove resource files from the folder you are analyzing.<\/p>\n

      <\/a>Using the console-based version<\/h2>\n

      If you would like to run the analysis for many applications, you can either run them one by one as described above or you can use the console version of the Portability Analyzer.<\/p>\n

      Note:<\/strong> You will get one report per invocation of the ApiPort.exe tool. If you prefer to get one report per application, you can automate the invocation either using\u00a0for<\/code>\u00a0in Batch or the\u00a0ForEach<\/code>\u00a0mechanism in PowerShell.<\/em><\/p>\n

      To run the console app:<\/p>\n

        \n
      1. Download and unzip\u00a0Console Portability Analyzer<\/a>.<\/li>\n
      2. From the command prompt run the following command specifying multiple directories, dlls, or executables:\n