Created
September 20, 2023 01:27
-
-
Save jzebedee/d5e6c726692b83baf68fb5fc241c2929 to your computer and use it in GitHub Desktop.
Why don't we test .NET Framework targets that involve compiled assemblies?
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Q: Why don't we test .NET Framework (`netXXX`, e.g., `net472`) targets that involve compiled assemblies? | |
| A: Because it doesn't work. | |
| The longer answer is that the `runtimes/` assembly resolution logic doesn't seem to work correctly on .NET Framework when a RID isn't specified. Native assets will be correctly copied into the appropriate `runtimes/` folder but the DllImport probing won't select for them if a RID is missing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment