AutoSkill 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.

install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt4_8/c-build-target-selection-strategy" ~/.claude/skills/ecnu-icalk-autoskill-c-build-target-selection-strategy && rm -rf "$T"
manifest: SkillBank/ConvSkill/english_gpt4_8/c-build-target-selection-strategy/SKILL.md
source content

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

  1. Small Programs: Default to recommending "Any CPU" for small, self-contained programs to ensure flexibility.
  2. Large/Legacy Software: For large or old software, analyze third-party component compatibility before deciding.
  3. 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.
  4. 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