If you copy from the samples, you should not have to spend an hour removing things you don't need. Keep styling minimal: the point of a sample is the code, not the CSS.
- CSS framework: use the Bootstrap version from the ASP.NET Core templates. No other CSS frameworks or themes.
- Duende styling (optional): copy the Bootstrap overrides for your Bootstrap version into the sample's
wwwroot/cssfolder, and reference it right afterbootstrap.min.css:
<link rel="stylesheet" href="~/lib/bootstrap/dist/css/bootstrap.min.css" />
<link rel="stylesheet" href="~/css/bootstrap-overrides.css" asp-append-version="true" />The Build workflow compiles every sample on each push to main. Pull requests build only the samples affected by the change; changes under .github/ or to shared build inputs (global.json, Directory.Build.props/.targets, Directory.Packages.props, nuget.config, .editorconfig) build every sample beneath them:
- every
.sln/.slnx(except the rootsamples.slnx) is built in its own job; MAUI and .NET Framework (OWIN) samples build on Windows (thewindows-latest-x64-16corelarger runner in the organization'sLargerunner group) - every npm project with a
package-lock.jsonrunsnpm ciandnpm run build
New samples are discovered automatically by discover-builds.cs (run it locally with dotnet run .github/scripts/discover-builds.cs).
Make sure a new sample has its own solution file (and a committed package-lock.json for npm clients) so it gets built.