Move .NET Core unmanaged APIs to /core folder

[gewarren]

The unmanaged APIs for debugging and profiling that were introduced in .NET Core were moved to the /core folder in #37206. The APIs for the other feature areas should also be checked and moved accordingly. APIs that can only be used on .NET Framework apps should stay in the /framework folder. If we decide to move all APIs that can be used on both implementations to the /core folder, then the applicable APIs for debugging/profiling should be moved too. Info from David Mason re: profiling APIs:

We still support almost all of the framework era APIs on coreclr, we have only deprecated a few related to assembly loading since it is much simpler in coreclr...

Re: other areas:

The ICorDebug and Metadata APIs are the same as ICorProfiler, they are almost entirely supported on both Framework and Core. The others I am not as familiar with, but I think some of them (Tblexp, fusion, strong naming, WMI) are only supported on Framework and some (hosting, COM) are supported on both but have had some significant changes that aren’t as straightforward to tease apart. We would have to get the respective owners involved to sign off on them.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 26be196d-e1a9-0589-e39a-271478e66b8a
• Version Independent ID: 8d532104-dca0-f853-ad90-4be287ab567a
• Content: Unmanaged API Reference - .NET Framework
• Content Source: docs/framework/unmanaged-api/index.md
• Product: dotnet-framework
• GitHub Login: @gewarren
• Microsoft Alias: dotnetcontent