Simple SDK for custom artifacts (EXEs / DLLs) generated by external tool

I'm trying to use the Microsoft.Build.NoTargets SDK to generate a project that builds a Rust cdylib (.dll / .so) and produces the following artifacts:

• foo.dll
• foo.pdb
• ...

What I'd like is to have a way to specify all of this in the most elegant way (not just tied to Rust) but the Microsoft.Build.NoTargets SDK explicitly disables the GetTargetPath target (and other stuff) and it makes you import the SDK manually (instead of just using <Project Sdk="...">) because it's intended to be a way to just launch some tools that produce no artifacts / assemblies.

So it would be nice to have a minimal SDK that just invokes two main targets (Build and Clean) and a target that allows specifying which generated files are to be copied transitively (with a folder structure relative from the build directory, like BUILD/res/foo.bin).

My concrete goal is to have a Rust (or Zig / whatever) native DLL project (libfoo-rs) that is referenced by a C# wrapper project (LibFoo) that gets used by a C# Exe project (FooApp) such that when running FooApp in VS, everything gets copied in the final Output directory.

Inizia leggendo il comportamento dell’SDK Microsoft.Build.NoTargets relativo a GetTargetPath e all’SDK importato manualmente. Definisci come devono funzionare i target minimi Build e Clean e come i file generati, come DLLs, PDBs e altri artefatti relativi, vengano propagati attraverso il wrapper C# fino alla directory di output finale di FooApp. Il lavoro è completato quando uno strumento esterno Rust, Zig o simile può compilare e pulire gli artefatti, mentre i progetti referenziati li copiano transitivamente.