search

AaronRobinsonMSFT / DNNE

Prototype native exports for a .NET Assembly.
MIT License
406 stars 41 forks source link

Allow the native library to be explicitly named #59

Closed sanny-io closed 3 years ago

sanny-io commented 3 years ago

Not sure if this is possible, but messing with post-build events and such to rename it isn't ideal. An option to explicitly set the name instead of a suffix would be much easier for automation.

AaronRobinsonMSFT commented 3 years ago

@sanny-io Is the idea that more than a suffix is needed ? I assume this has more to do with the desire to name the native export binary as you want it rather than any real technical issue. Can you provide an example of how the native export binary is named vs the managed assembly?

sanny-io commented 3 years ago

Correct. The native export binary appends NE to the managed assembly's name through the DnneNativeBinarySuffix property. What I propose is instead a property to outright set the generated binary's name. Perhaps a new DnneNativeBinaryName property that defaults to <DnneNativeBinaryName>$(TargetName)NE$(TargetExt)</DnneNativeBinaryName >

Managed name: managed.dll Native binary: managedNE.dll <-- Allow to set the entire name, not just a suffix.