Simple SDK for custom artifacts (EXEs / DLLs) generated by external tool
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system
Research direction
Start by reading the Microsoft.Build.NoTargets SDK behavior around GetTargetPath and the manually imported SDK. Define how the minimal Build and Clean targets should work and how generated files such as DLLs, PDBs, and other relative artifacts propagate through the C# wrapper into FooApp's final output directory. Done means an external Rust, Zig, or similar tool can build and clean artifacts while referenced projects copy them transitively.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C#
- Stars
- 512
- Forks
- 94
- Avg merge
- 6h 12m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/MSBuildSdks
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/MSBuildSdks#652 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/MSBuildSdks#646 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/MSBuildSdks#644 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/MSBuildSdks#642 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/MSBuildSdks#635 ·
All issues in microsoft/MSBuildSdks
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PCL-Community/PCL-CE#3652 ·
Maintainers usually reply within 1 day
-
area:frontend bug FE P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
klasolsson81/jobbliggaren#2010 ·
Maintainers usually reply within 1 day
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
area: homeblaze type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
RicoSuter/Namotion.Interceptor#630 ·
Maintainers usually reply within 1 day
-
Akka.Hosting enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100