Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / microsoft/dotnet-apiport issues and pull requests

#1024 - Portability analyzer not running

Issue - State: closed - Opened by eddie2302 about 2 years ago - 1 comment

#1023 - Update changelog for 2.8 release

Pull Request - State: closed - Opened by brandonh-msft about 2 years ago

#1022 - Release for VSIX offline capability

Pull Request - State: closed - Opened by brandonh-msft about 2 years ago

#1019 - here was an unknown error code from the service: 'InternalServerError'.

Issue - State: closed - Opened by Robbbbin0309 about 2 years ago - 4 comments

#1017 - Bump Newtonsoft.Json from 12.0.3 to 13.0.1 in /tests/lib/Microsoft.Fx.Portability.Cci.Tests

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago - 1 comment
Labels: dependencies

#1016 - Bump Newtonsoft.Json from 12.0.3 to 13.0.1 in /tests/lib/Microsoft.Fx.Portability.Tests

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago - 1 comment
Labels: dependencies

#1012 - Bump Newtonsoft.Json from 12.0.3 to 13.0.1 in /tests/ApiPort/ApiPortVS.Tests

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago - 1 comment
Labels: dependencies

#1011 - Some small corrections in the README.md file.

Pull Request - State: closed - Opened by dlemstra over 2 years ago

#1010 - Fix broken links of Channel 9

Pull Request - State: closed - Opened by chi-qin over 2 years ago

#1005 - Report falsely claims target types are not supported when they *are*

Issue - State: closed - Opened by AArnott over 2 years ago - 3 comments

#1004 - InternalServerError when making up a target platform

Issue - State: closed - Opened by AArnott over 2 years ago - 1 comment

#1003 - Refactor to shared projects and add new VSIX project for Visual Studio 2022

Pull Request - State: closed - Opened by BertanAygun almost 3 years ago - 3 comments

#1002 - Incompatible with VS 2022 RC?

Issue - State: closed - Opened by lavanyadeepak almost 3 years ago - 5 comments

#1001 - .NET 6 support

Issue - State: closed - Opened by omajid almost 3 years ago - 7 comments

#999 - Fix APIScan

Pull Request - State: closed - Opened by Lxiamail about 3 years ago - 1 comment

#997 - APIScan fails in VSEngSS-MicroBuild2019-1ES pool

Issue - State: closed - Opened by Lxiamail about 3 years ago - 1 comment

#993 - Analyzer Erroneously Reports Incompatibilities for EF Core projects

Issue - State: closed - Opened by JeremyLikness about 3 years ago - 9 comments
Labels: catalog

#988 - ApiPort cannot analyze .NET Framework 2.0 assemblies

Issue - State: closed - Opened by aov-mx about 3 years ago - 1 comment

#985 - Visual Studio 2022 Support

Issue - State: closed - Opened by scottkuhl about 3 years ago - 6 comments

#983 - Resolves: Add GitHub Codespaces configuration

Pull Request - State: closed - Opened by szlatkow about 3 years ago - 2 comments

#982 - Add GitHub Codespaces configuration

Issue - State: closed - Opened by szlatkow about 3 years ago - 1 comment

#976 - Crash when running on solution in VS 2019

Issue - State: closed - Opened by Kalhorn over 3 years ago - 1 comment

#970 - Update privacy statement

Pull Request - State: closed - Opened by Lxiamail over 3 years ago

#969 - Port order seems backwards

Issue - State: closed - Opened by MisinformedDNA over 3 years ago - 1 comment

#968 - Variances between CLI and GUI versions of ApiPort

Issue - State: closed - Opened by timrhaynes over 3 years ago - 1 comment

#958 - Accuracy issue - .NET Framework 4.8

Issue - State: closed - Opened by PheelaV over 3 years ago - 1 comment

#957 - Some non-.NET Framework assemblies are unexpectedly skipped on apiport 2.8.10

Issue - State: closed - Opened by Lxiamail over 3 years ago - 1 comment
Labels: regression

#954 - BreakingChangeParser needs to be updated

Issue - State: closed - Opened by Youssef1313 almost 4 years ago - 1 comment

#953 - -VsDevCmdPath does not exist

Issue - State: closed - Opened by MeikelLP almost 4 years ago - 1 comment

#952 - System.EnterpriseServices.Wrapper.dll - unexpected error

Issue - State: closed - Opened by suchoss almost 4 years ago - 3 comments

#923 - DGML generation seems to be broken

Issue - State: closed - Opened by vruss about 4 years ago - 5 comments

#922 - Microsoft.VisualStudio.TestTools.UnitTesting supported in .NET Standard + PE, but not in .NET Core + PE

Issue - State: closed - Opened by stogle about 4 years ago - 3 comments
Labels: catalog

#915 - System.CommandLine is very out of date

Issue - State: closed - Opened by twsouthwick about 4 years ago - 2 comments

#911 - ApiPort roadmap

Issue - State: closed - Opened by Lxiamail about 4 years ago - 3 comments

#901 - Added the retrieval of the exceptions.bin file to the init script.

Pull Request - State: closed - Opened by LoopedBard3 about 4 years ago - 4 comments

#899 - MemoryCache is reported incompatible with netstandard2.0

Issue - State: closed - Opened by zitcomdev about 4 years ago - 6 comments
Labels: catalog

#896 - DGML Generation Broken

Issue - State: closed - Opened by eslam-a-elsawy about 4 years ago - 19 comments

#892 - Analyze NuGet package dependency

Issue - State: closed - Opened by shirishwagh83 over 4 years ago - 3 comments
Labels: Feature Request

#884 - Instructions to build on Linux

Issue - State: closed - Opened by ghost over 4 years ago - 6 comments

#880 - How to run the ApiPort tool from macOS ?

Issue - State: closed - Opened by syberkitten over 4 years ago - 2 comments
Labels: client-side

#868 - The Visual Studio Extension makes it hard to manage reports

Issue - State: closed - Opened by martingbrown over 4 years ago - 4 comments
Labels: bug, vsix, poachable

#861 - Json format APIPort report doesn't include the analyzed assemblyname

Issue - State: closed - Opened by Lxiamail over 4 years ago - 3 comments
Labels: report

#858 - how many calls an .NET API was usage is not report by APIPort tool

Issue - State: closed - Opened by Lxiamail over 4 years ago - 1 comment
Labels: Feature Request

#857 - Reports unsupported .Net Core 3.1 issues with Microsoft.IdentityModel.Clients.ActiveDirectory

Issue - State: closed - Opened by ghost over 4 years ago - 2 comments
Labels: catalog

#855 - Add option to treat EditorBrowsable attribute as meaning api isn't available

Issue - State: closed - Opened by mconnew over 4 years ago - 1 comment
Labels: Feature Request

#854 - Improve guidance for unsupported properties with default values

Issue - State: closed - Opened by mconnew over 4 years ago - 1 comment
Labels: Feature Request

#853 - Reports unsupported methods in Newtonsoft & SharpZip

Issue - State: closed - Opened by ghost over 4 years ago - 2 comments
Labels: catalog

#847 - Inherited APIs are reported as not supported

Issue - State: closed - Opened by Lxiamail almost 5 years ago - 3 comments

#832 - advice on "unsupported" APIs

Issue - State: closed - Opened by jol64 almost 5 years ago - 2 comments

#821 - PublicKeyToken parsing doesn't handle not strong named assembly

Issue - State: closed - Opened by Lxiamail almost 5 years ago - 1 comment

#818 - On vsixgallery.com, links to documentation are broken

Issue - State: closed - Opened by akeeton almost 5 years ago - 2 comments

#813 - DGML reference assembly APICounts issues

Issue - State: closed - Opened by Lxiamail almost 5 years ago - 1 comment

#810 - Clean up locks in DependencyFinderEngine.cs

Issue - State: closed - Opened by Lxiamail almost 5 years ago - 1 comment

#797 - Have option for listing the class (and maybe line in code) of the found incompatibility.

Issue - State: closed - Opened by wmanning about 5 years ago - 1 comment
Labels: Feature Request

#788 - fix binskim bug for HighEntropyVACheck issue

Pull Request - State: closed - Opened by Lxiamail about 5 years ago - 8 comments

#782 - Portability Analysis Results always starts empty

Issue - State: closed - Opened by chlowell about 5 years ago - 1 comment
Labels: bug, vsix

#781 - Installing on VS2017 15.9.13, no options available to run it

Issue - State: closed - Opened by peterlukerow about 5 years ago - 3 comments
Labels: vsix

#778 - ApiPort release download zip file doesn't contain .NET Core version

Issue - State: closed - Opened by Lxiamail about 5 years ago - 1 comment

#774 - "Unresolved assembly" or "missing assembly" in the report is confusing

Issue - State: closed - Opened by Lxiamail over 5 years ago - 4 comments
Labels: report

#773 - Recommended changes in the report are not useful

Issue - State: closed - Opened by Lxiamail over 5 years ago - 2 comments
Labels: report

#771 - WPF APIs are reported not supported on .NET Core+Platform Extension, but supported on .NET Core

Issue - State: closed - Opened by Lxiamail over 5 years ago - 1 comment
Labels: catalog, report

#770 - Azure SDK for .NET libraries are reported as not compatible with .NET Framework

Issue - State: closed - Opened by Lxiamail over 5 years ago - 1 comment
Labels: catalog, report

#722 - false warning for System.Threading.Tasks.Dataflow.DataflowBlockOptions.set_EnsureOrdered(System.Boolean)

Issue - State: closed - Opened by springy76 almost 6 years ago - 4 comments
Labels: catalog

#702 - why neither "ASP.NET Core 2.1" nor ".NET Core + Platform Extensions 2.1"?

Issue - State: closed - Opened by springy76 about 6 years ago - 11 comments
Labels: catalog, Suggestion

#692 - Detect all competability issues with a specific DLL file

Issue - State: closed - Opened by Lidanha about 6 years ago - 5 comments
Labels: enhancement, help wanted, client-side

#690 - Potential Feature: Generating report on the basis of application namespaces

Issue - State: closed - Opened by shailesh757 about 6 years ago - 2 comments
Labels: enhancement, server-side, report

#668 - Publish the client as a .NET Core global tool

Issue - State: closed - Opened by jeremymeng over 6 years ago - 11 comments
Labels: enhancement, client-side, command-line

#640 - Potential feature: APIPort helper when nuget resolves an assembly from a different TFM

Issue - State: closed - Opened by ericstj over 6 years ago - 3 comments
Labels: enhancement, client-side

#631 - Solution-level analysis doesn't allow for analysing of references

Issue - State: closed - Opened by IanKemp over 6 years ago - 1 comment
Labels: enhancement, vsix, client-side

#625 - "Recommended changes" should point users to Microsoft.Windows.Compatibility package where appropriate

Issue - State: closed - Opened by IanKemp over 6 years ago - 3 comments
Labels: catalog

#615 - Breaking Changes output should consider the assembly's target framework

Issue - State: closed - Opened by billwert over 6 years ago - 1 comment
Labels: enhancement

#602 - Portability Analyzer ignores build flag?

Issue - State: closed - Opened by JerkerPihl over 6 years ago - 1 comment
Labels: bug, vsix, client-side

#571 - APIPort flags API as missing when override is missing

Issue - State: closed - Opened by ericstj over 6 years ago - 1 comment
Labels: catalog

#496 - Add command to analyze .Net Standard 2 library against the missing of not implemented api by net461

Issue - State: closed - Opened by moh-hassan almost 7 years ago - 3 comments
Labels: catalog

#489 - considers Newtonsoft.Json to be available on Core, but not on Desktop.

Issue - State: closed - Opened by danmoseley about 7 years ago - 5 comments
Labels: catalog

#484 - Unclear how to test ASP.NET Core 2.0 compatibility

Issue - State: closed - Opened by oising about 7 years ago - 3 comments
Labels: catalog

#450 - Feature request: API Port should scan installed nuget packages

Issue - State: closed - Opened by aszego about 7 years ago - 3 comments
Labels: enhancement

#445 - Apis that are now supported

Issue - State: closed - Opened by mikes-gh over 7 years ago - 2 comments
Labels: catalog

#427 - .NetCoreApp TFM is not recognized

Issue - State: closed - Opened by tarekgh over 7 years ago - 9 comments
Labels: enhancement, cost-small, client-side, command-line

#416 - Feature Request: include major unsupported components in report summary

Issue - State: closed - Opened by jeremymeng over 7 years ago - 2 comments
Labels: enhancement, server-side, cost-medium, report

#393 - Clarify that breaking changes addressed in servicing may not be reported

Issue - State: closed - Opened by mjrousos over 7 years ago - 2 comments
Labels: server-side, cost-small, client-side

#362 - Add description of .NET platform targets

Issue - State: closed - Opened by conniey almost 8 years ago - 4 comments
Labels: enhancement, server-side, catalog, cost-small, report