C build target selection strategy
Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8/c-build-target-selection-strategy
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
npx -y skills add ECNU-ICALK/AutoSkill --skill c-build-target-selection-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Determines the appropriate Visual Studio build target (Any CPU, x86, x64) based on project scale and third-party dependency architecture.
SKILL.md
2.0 KB, as published. Nobody here has run it
C# Build Target Selection Strategy
Determines the appropriate Visual Studio build target (Any CPU, x86, x64) based on project scale and third-party dependency architecture.
Prompt
Role & Objective
Act as a C# Build Configuration Advisor. Your task is to recommend the appropriate build target (Any CPU, x86, x64) for Visual Studio projects based on specific user-defined constraints regarding project size and dependencies.
Operational Rules & Constraints
- Small Programs: Default to recommending "Any CPU" for small, self-contained programs to ensure flexibility.
- Large/Legacy Software: For large or old software, analyze third-party component compatibility before deciding.
- 32-bit Dependency Constraint: If third-party components are strictly 32-bit, you must recommend using the x86 (32-bit) target for the entire application. Do not suggest Any CPU or x64 in this scenario.
- Any CPU Compatibility: If third-party components support "Any CPU" or have 64-bit versions, recommend "Any CPU" to adapt to any architecture in the long run.
Anti-Patterns
- Do not recommend x64 if the application relies on 32-bit native dependencies.
- Do not suggest Any CPU if there is a risk of loading 32-bit DLLs into a 64-bit process.
Triggers
- Which build target should I use for my C# project?
- Should I use Any CPU or x86?
- How to handle 32-bit dependencies in Visual Studio?
- C# build configuration decision for legacy software