Containerize Aspnet Framework
Produce Windows-container Dockerfiles for legacy ASP.NET .NET Framework apps so a solo builder can package IIS-hosted sites for controlled ship targets without confusing them with .NET Core images.
Overview
Containerize ASP.NET Framework is an agent skill for the Ship phase that creates Dockerfile and companion container files tailored to an ASP.NET .NET Framework project on Windows Server containers.
Install
npx skills add https://github.com/github/awesome-copilot --skill containerize-aspnet-frameworkWhat is this skill?
- Explicitly targets ASP.NET .NET Framework on Windows containers—not .NET Core/Linux patterns
- Configurable Windows Server SKU (Core vs Full) and version (2022, 2019, 2016)
- Settings-driven prompt: project .csproj path and optional advanced containerization toggles with documented defaults
- Creates Dockerfile and related container files scoped to changes required for Windows Docker run
- Warns that Framework containerization differs materially from Core container workflows
Adoption & trust: 8.4k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You still run .NET Framework on IIS and need Docker packaging, but generic container skills keep producing Linux or .NET Core images that will not run your site.
Who is it for?
Solo maintainers shipping legacy ASP.NET Framework web apps who must deploy on Windows containers with explicit Server Core or Full SKUs.
Skip if: New .NET 8 ASP.NET Core apps on Linux, serverless-only deploys with no containers, or teams unwilling to run Windows container hosts.
When should I use this skill?
You need to containerize an ASP.NET .NET Framework project with Dockerfile and related files customized from explicit containerization settings.
What do I get? / Deliverables
You receive Windows-oriented Dockerfile and .dockerignore-style artifacts aligned to your .csproj and chosen Windows Server base image settings.
- Dockerfile tuned for Windows ASP.NET Framework runtime
- Companion containerization files such as .dockerignore where applicable
- Configuration notes implied by filled containerization settings
Recommended Skills
Journey fit
Ship is the canonical phase because containerization is a release artifact step—locking runtime OS, IIS, and framework versions before deployment—not feature coding. Launch subphase fits first runnable container images and environment-specific Docker settings that unblock deployment pipelines and hosting choices.
How it compares
Use instead of copy-pasted Linux ASP.NET Core Docker snippets that ignore IIS and .NET Framework servicing baselines.
Common Questions / FAQ
Who is containerize-aspnet-framework for?
Indie builders and small teams with .csproj-based ASP.NET Framework apps who need Windows Docker images for repeatable shipping.
When should I use containerize-aspnet-framework?
In Ship launch when you are defining Dockerfiles before registry push, CI build steps, or handing images to a Windows container host.
Is containerize-aspnet-framework safe to install?
It edits or adds container build files in your repo—review exposed ports, secrets, and base image pins; see the Security Audits panel on this Prism page for the skill package.
SKILL.md
READMESKILL.md - Containerize Aspnet Framework
# ASP.NET .NET Framework Containerization Prompt Containerize the ASP.NET (.NET Framework) project specified in the containerization settings below, focusing **exclusively** on changes required for the application to run in a Windows Docker container. Containerization should consider all settings specified here. **REMEMBER:** This is a .NET Framework application, not .NET Core. The containerization process will be different from that of a .NET Core application. ## Containerization Settings This section of the prompt contains the specific settings and configurations required for containerizing the ASP.NET (.NET Framework) application. Prior to running this prompt, ensure that the settings are filled out with the necessary information. Note that in many cases, only the first few settings are required. Later settings can be left as defaults if they do not apply to the project being containerized. Any settings that are not specified will be set to default values. The default values are provided in `[square brackets]`. ### Basic Project Information 1. Project to containerize: - `[ProjectName (provide path to .csproj file)]` 2. Windows Server SKU to use: - `[Windows Server Core (Default) or Windows Server Full]` 3. Windows Server version to use: - `[2022, 2019, or 2016 (Default 2022)]` 4. Custom base image for the build stage of the Docker image ("None" to use standard Microsoft base image): - `[Specify base image to use for build stage (Default None)]` 5. Custom base image for the run stage of the Docker image ("None" to use standard Microsoft base image): - `[Specify base image to use for run stage (Default None)]` ### Container Configuration 1. Ports that must be exposed in the container image: - Primary HTTP port: `[e.g., 80]` - Additional ports: `[List any additional ports, or "None"]` 2. User account the container should run as: - `[User account, or default to "ContainerUser"]` 3. IIS settings that must be configured in the container image: - `[List any specific IIS settings, or "None"]` ### Build configuration 1. Custom build steps that must be performed before building the container image: - `[List any specific build steps, or "None"]` 2. Custom build steps that must be performed after building the container image: - `[List any specific build steps, or "None"]` ### Dependencies 1. .NET assemblies that should be registered in the GAC in the container image: - `[Assembly name and version, or "None"]` 2. MSIs that must be copied to the container image and installed: - `[MSI names and versions, or "None"]` 3. COM components that must be registered in the container image: - `[COM component names, or "None"]` ### System Configuration 1. Registry keys and values that must be added to the container image: - `[Registry paths and values, or "None"]` 2. Environment variables that must be set in the container image: - `[Variable names and values, or "Use defaults"]` 3. Windows Server roles and features that must be installed in the container image: - `[Role/feature names, or "None"]` ### File System 1. Files/directories that need to be copied to the container image: - `[Paths relative to project root, or "None"]` - Target location in container: `[Container paths, or "Not applicable"]` 2. Files/directories to exclude from containerization: - `[Paths to exclude, or "None"]` ### .dockerignore Configuration 1. Patterns to include in the `.dockerignore` file (.dockerignore will already have common defaults; these are additional patterns): - Additional patterns: `[List any additional patterns, or "None"]` ### Health Check Configuration 1. Health check endpoint: - `[Health check URL path, or "None"]` 2. Health check interval and timeout: - `[Interval and timeout values,