dotnet-apiport icon indicating copy to clipboard operation
dotnet-apiport copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Report falsely claims target types are not supported when they *are*

Open AArnott opened this issue 2 years ago • 2 comments

Running APIPort against at least one directory of assemblies produced a report of 17 incompatibilities, but every single one is a false positive. Here are the groupings of APIs that apiport apparently is ignorant of being available on .NET 5:

  • MSBuild (T:Microsoft.Build.Utilities.TaskLoggingHelper)
  • MEFv1 (T:System.ComponentModel.Composition.AttributedModelServices)
  • ADO.NET? (T:System.Data.SqlClient.SqlConnection)
  • WPF (T:System.Windows.Controls.VirtualizingStackPanel)

AArnott avatar Jan 28 '22 00:01 AArnott

What target framework are you comparing against? If I remember correctly, the platform extensions would include Windows specific (and hopefully WPF stuff). Not sure if that would explain all of the missing types, though.

twsouthwick avatar Feb 03 '22 17:02 twsouthwick

I was using ".NET, Version=5.0" at the time. When I use ".NET + Platform Extensions, Version=5.0" MSBuild and WinForms types still show up as incompatible, though I didn't see MEFv1 or ADO.NET any more (although maybe I just missed them for all the other noise and valid APIs that were listed.)

AArnott avatar Feb 03 '22 21:02 AArnott

Closing as API Port was deprecated in favor of binary analysis in .NET Upgrade Assistant.

terrajobst avatar Nov 15 '22 23:11 terrajobst