'Do I still the api-ms redirect DLLs in Windows 10/.NET 6
Every application I publish as self-contained with .NET 6 and before outputs a large set of api-ms* assemblies/DLLs. While I understand for what reason they are here, I thought the original reason was that API call from former P/Invokes are redirected to newer API calls.
I assumed that increasing the RuntimeIdentifier to win10 or even higher versions, like net5.0-windows10.0.22000.0 gets rid of them but they are still there.
What is the reason why they are still there even in never version and can I safely delete them? I would also be nice if there would be a good reference to read about. I'm not sure if something is written in "Windows Internals" or if I missed it.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|