Run any Skill in Manus with one click

credfeto-dotnet-publish

Stars2

Forks0

UpdatedJuly 2, 2026 at 13:28

Enable trimming and AOT publishing on .NET executable projects in the correct staged order. Use when working on a .NET project that produces a publishable executable (OutputType=Exe or WinExe), or when asked to enable PublishTrimmed, PublishAot, or fix IL2xxx/IL3xxx warnings.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

credfeto

credfeto/credfeto-ai-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	credfeto-dotnet-publish
description	Enable trimming and AOT publishing on .NET executable projects in the correct staged order. Use when working on a .NET project that produces a publishable executable (OutputType=Exe or WinExe), or when asked to enable PublishTrimmed, PublishAot, or fix IL2xxx/IL3xxx warnings.

.NET Publishing: Trimming and AOT

When working on a .NET project that produces a publishable executable (OutputType=Exe or OutputType=WinExe), follow these steps in order.

1. Enable Trimming First

Add <PublishTrimmed>true</PublishTrimmed> to the project file and verify the project builds without trim warnings or errors.

Fix all IL2xxx trim-analysis warnings before committing.
Replace reflection-based patterns with source-generated equivalents — for example, replace JsonSerializer usage with a JsonSerializerContext annotated with [JsonSerializable].
Apply [DynamicallyAccessedMembers] only where reflection is genuinely unavoidable and cannot be replaced with a source generator.
Do not suppress trim warnings — treat them as blocking, consistent with <TreatWarningsAsErrors>true</TreatWarningsAsErrors>.

2. Enable AOT Only After Trimming Is Clean

Once <PublishTrimmed>true</PublishTrimmed> builds without warnings, replace it with <PublishAot>true</PublishAot> (AOT implies trimming; both properties do not need to be set simultaneously).

Fix all IL3xxx AOT-compatibility warnings.
Remove any runtime code generation: Emit, DynamicMethod, Expression.Compile, CSharpCodeProvider, etc.
Verify that every third-party package used by the executable has AOT-compatible code paths. Check for IsAotCompatible=true in the package metadata or a corresponding [RequiresUnreferencedCode] annotation indicating the incompatibility.
Do not suppress AOT warnings — treat them as blocking.

3. If Blocked by an Incompatible Third-Party Dependency

Raise a GitHub issue in the current repository describing the incompatibility (package name, version, and the specific warning or error), then stop. Do not work around the incompatibility by suppressing warnings or downgrading the property.

General Warning Rules

Every project must build with <TreatWarningsAsErrors>true</TreatWarningsAsErrors>.
Never use #pragma warning disable <ID>, <NoWarn>, <WarningsNotAsErrors>, or [SuppressMessage] without explicit written permission from the repo owner.
If a warning fires, fix the root cause. If the fix is non-obvious, raise a GitHub issue rather than suppressing the warning.

More from this repository

same repository

credfeto-deprecation-handling

credfeto/credfeto-ai-skills

Triage deprecation warnings seen in test output — fix ones caused by your change immediately, track pre-existing ones with a GitHub issue. Use whenever a deprecation warning (framework or runtime warning about a deprecated API) appears while running tests.

2026-07-122

credfeto-dotnet-test-patterns

credfeto/credfeto-ai-skills

Write .NET unit tests using FunFair.Test.Common/FunFair.Test.Infrastructure base classes, mocking helpers, date sources, and xunit assertion patterns instead of hand-rolled equivalents. Use whenever writing or reviewing a .NET unit test (a *.Tests project).

2026-07-122

credfeto-git-branch

credfeto/credfeto-ai-skills

Create, name, and maintain git branches — branching rules, Conventional Commits-style branch naming, rebasing against main, resuming interrupted work, and resolving version conflicts in dependency manifests during merges/rebases. Use when starting new work, creating a branch, resuming work on an existing branch, rebasing, or resolving merge conflicts.

2026-07-122

credfeto-git-commit

credfeto/credfeto-ai-skills

Commit and push changes safely — branch checks, build/test gates, Conventional Commits format, and push cadence. Use whenever about to commit, stage, or push changes in any repository, or when acting as the Committer agent.

2026-07-122

credfeto-github-issue

credfeto/credfeto-ai-skills

Create and manage GitHub issues correctly — duplicate search, planned descriptions, priority/status labels, assignment, and the Blocked label rules for AI-initiated issues, including the mandatory tracking issue required before starting any ad-hoc task. Use when asked to create a GitHub issue, when raising an issue autonomously, when a human asks you to do something and no existing issue or PR is already specified, when a PR or issue comment asks you to raise an issue, when selecting the next issue to work on, or when asking a blocking question and needing to mark an item Blocked.

2026-07-122

credfeto-performance-benchmarking

credfeto/credfeto-ai-skills

Design and optimise performance-critical code, and back optimisations with committed benchmarks and measured allocation thresholds. Use when writing or optimising performance-critical code, or when asked to add or update a benchmark.

2026-07-122

name	credfeto-dotnet-publish
description	Enable trimming and AOT publishing on .NET executable projects in the correct staged order. Use when working on a .NET project that produces a publishable executable (OutputType=Exe or WinExe), or when asked to enable PublishTrimmed, PublishAot, or fix IL2xxx/IL3xxx warnings.

.NET Publishing: Trimming and AOT

When working on a .NET project that produces a publishable executable (OutputType=Exe or OutputType=WinExe), follow these steps in order.

1. Enable Trimming First

Add <PublishTrimmed>true</PublishTrimmed> to the project file and verify the project builds without trim warnings or errors.

Fix all IL2xxx trim-analysis warnings before committing.
Replace reflection-based patterns with source-generated equivalents — for example, replace JsonSerializer usage with a JsonSerializerContext annotated with [JsonSerializable].
Apply [DynamicallyAccessedMembers] only where reflection is genuinely unavoidable and cannot be replaced with a source generator.
Do not suppress trim warnings — treat them as blocking, consistent with <TreatWarningsAsErrors>true</TreatWarningsAsErrors>.

2. Enable AOT Only After Trimming Is Clean

Once <PublishTrimmed>true</PublishTrimmed> builds without warnings, replace it with <PublishAot>true</PublishAot> (AOT implies trimming; both properties do not need to be set simultaneously).

Fix all IL3xxx AOT-compatibility warnings.
Remove any runtime code generation: Emit, DynamicMethod, Expression.Compile, CSharpCodeProvider, etc.
Verify that every third-party package used by the executable has AOT-compatible code paths. Check for IsAotCompatible=true in the package metadata or a corresponding [RequiresUnreferencedCode] annotation indicating the incompatibility.
Do not suppress AOT warnings — treat them as blocking.

3. If Blocked by an Incompatible Third-Party Dependency

General Warning Rules

Every project must build with <TreatWarningsAsErrors>true</TreatWarningsAsErrors>.
Never use #pragma warning disable <ID>, <NoWarn>, <WarningsNotAsErrors>, or [SuppressMessage] without explicit written permission from the repo owner.
If a warning fires, fix the root cause. If the fix is non-obvious, raise a GitHub issue rather than suppressing the warning.