Native AOT + unmanaged static lib interop: DLL required while development phase?

[thewavelength]

In my final deployment, I want to link against an unmanaged static lib as written in the Native code interop article. As far as I understand, static lib linking is not possible while being in "development phase", as it's a feature of the "publish" self-contained executable step. I want to normally debug my application while developing it.

1. Is it really the "correct" way to link dynamically in development phase and link statically at publish time?
2. Does this mean I have to have my libraries available both as static and dynamic versions to have a proper development phase?
3. Are there ideas for future ways to improve that experience?