You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reusable skill for .NET upgrades, C# feature reviews, NuGet, CI, and Native AOT.
name
dotnet-upgrade-csharp-sweep
description
Use for repository-wide .NET upgrades, NuGet and CI changes, C# feature reviews, and Native AOT validation.
.NET upgrade and C# feature sweep
Treat an upgrade as a repository-wide compatibility change, not a version-string
replacement. Adopt new language features where they improve the actual code.
Distinguish SDK/runtime upgrades, language features, library APIs, and measured
Incremental builds: deep research and implementation guidance
Executive Summary
Incremental builds are not one mechanism. In practice there are at least five reuse layers: up-to-date skipping, persistent task/action caching, in-process bundler reuse, page/route-level static-output reuse, and request-time regeneration. Systems that work well distinguish those layers explicitly instead of expecting one cache to solve every performance problem.[^1][^2][^3][^8][^9][^14][^16]
The strongest common rule across build systems is that reuse must be a function of declared inputs, outputs, configuration, and runtime context. Gradle, MSBuild, Bazel, Pants, Nx, and Turborepo all make correctness depend on explicit dependency modeling, deterministic work, and conservative invalidation.[^1][^3][^4][^5][^6][^7]
For static site generators, the hardest problems are hidden dependencies, global fan-out from shared data, path-sensitive caches, and the temptation to blur build-time incrementality with runtime regen
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is intended as a quick reference and showcase. For more complete info, see John Gruber's original spec and the Github-flavored Markdown info page. This cheatsheet is modified from Joshua Pekera'a cheat sheet for "Markdown Here", but this page is just GitHub Flavored Markdown
Proposed new APIs for the `IDistributedCache` interface.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Minimal API — Azure Cosmos DB repository-pattern .NET SDK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters