Skip to content
AI & Agents
Skill

/containerize-aspnet-framework

Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project.

From plugin
awesome-copilot
39k200 skills200 agents
Install
$ npx -y skills add github/awesome-copilot --skill containerize-aspnet-framework --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/containerize-aspnet-framework

Context preview

The summary Claude sees to decide when to auto-load this skill.

Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project.

SKILL.md

containerize-aspnet-framework.SKILL.md
name: containerize-aspnet-framework
description: 'Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project.'

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, or "Use defaults"]`

Additional Instructions

1. Other instructions that must be followed to containerize the project:

  • `[Specific requirements, or "None"]`

2. Known issues to address:

  • `[Describe any known issues, or "None"]`

Scope

  • ✅ App configuration modification to ensure config builders are used to read app settings and connection strings from the environment variables
  • ✅ Dockerfile creation and configuration for an ASP.NET application
  • ✅ Specifying multiple stages in the Dockerfile to build/publish the application and copy the output to the final image
  • ✅ Configuration of Windows container platform compatibility (Windows Server Core or Full)
  • ✅ Proper handling of dependencies (GAC assemblies, MSIs, COM components)
  • ❌ No infrastructure setup (assumed to be handled separately)
  • ❌ No code changes beyond those required for containerization

Execution Process

1. Review the containerization settings above to understand the containerization requirements 2. Create a `progress.md` file to track changes with check marks 3. Determine the .NET Framework version from the project's .csproj file by checking the `TargetFrameworkVersion` element 4. Select the appropriate Windows Server container image based on:

  • The .NET Framework version detected from the project
  • The Windows Server SKU specified in containerization settings (Core or Full)
  • The Windows Server version specified in containerization settings (2016, 2019, or 2022)
  • Windows Server Core tags can be found at: https://github.com/microsoft/dotnet-framework-docker/blob/main/README.aspnet.md#full-tag-listing

5. Ensure that required NuGet packages are installed. **DO NOT** install these if they are missing. If they are not installed, the user must install them manually. If they are not installed, pause executing this prompt and ask the user to install them using the Visual Studio NuGet Package Manager or Visual Studio package manager console. The following packages are require

Read more
Ships withawesome-copilot

A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.

Get the whole plugin

Other skills on awesome-copilot.