Does Native AOT support exporting apis by serial number?

[Gaoyifei1011]

Does Native AOT support exporting apis by serial number?

--------------------------

Native AOT 支持以序号导出 API 吗？

---

c++ generated Native DLLS can support ordinal export, such as Uxtheme.dll 135 API, 136 API used as the default right-click menu dark theme.

--------------------------

c++ 生成的 Native dll 可以支持以序号导出，比如 Uxtheme.dll 的 135 API，136 API 用作为默认右键菜单的深色主题。

---

[LibraryImport(Uxtheme, EntryPoint = "#135", SetLastError = false), PreserveSig]
public static partial void SetPreferredAppMode(PreferredAppMode preferredAppMode);

[LibraryImport(Uxtheme, EntryPoint = "#136", SetLastError = false), PreserveSig]
public static partial void FlushMenuThemes();

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

[hez2010]

You can manipulate the exports file by yourself with MSBuild, and update it before the NativeAOT compiler calls the linker.
For example:

  <Target Name="ReadExportsFile" BeforeTargets="LinkNative" DependsOnTargets="IlcCompile">
    <ReadLinesFromFile File="$(ExportsFile)">
      <Output TaskParameter="Lines" ItemName="_ExportsFileContent" />
    </ReadLinesFromFile>
  </Target>

  <Target Name="WriteExportsFile" BeforeTargets="LinkNative" DependsOnTargets="ReadExportsFile">
    <ItemGroup>
      <_ExportsFileContent Remove="Foo" />
      <_ExportsFileContent Include="Foo @42" />
    </ItemGroup>
    <WriteLinesToFile File="$(ExportsFile)" Lines="@(_ExportsFileContent)" Overwrite="True" />
  </Target>

Verify with dumpbin:

    ordinal hint RVA      name

         43    0 000DE380 DotNetRuntimeDebugHeader = DotNetRuntimeDebugHeader
         42    1 00001430 Foo = Foo

[KalleOlaviNiemitalo]

That WriteExportsFile target looks like the duplicate file write BuildCheck dotnet/msbuild#9881 dotnet/msbuild#10184 should warn about it.

[hez2010]

That WriteExportsFile target looks like the duplicate file write BuildCheck dotnet/msbuild#9881 dotnet/msbuild#10184 should warn about it.

Nope. The exports file was originally not written by an MSBuild target. Instead, it was written by ilc directly.