containerize-aspnet-framework

Name: containerize-aspnet-framework
Author: github

8.6kinstalls4.6kforks

How to install containerize-aspnet-framework?

github/awesome-copilot/containerize-aspnet-framework

$npx -y skills add github/awesome-copilot --skill containerize-aspnet-framework

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# ASP.NET .NET Framework Containerization Prompt
2
3	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.
4
5	REMEMBER: This is a .NET Framework application, not .NET Core. The containerization process will be different from that of a .NET Core application.
6
7	## Containerization Settings
8
9	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.
10
11	Any settings that are not specified will be set to default values. The default values are provided in `[square brackets]`.
12
13	### Basic Project Information
14	1. Project to containerize:
15	- `[ProjectName (provide path to .csproj file)]`
16
17	2. Windows Server SKU to use:
18	- `[Windows Server Core (Default) or Windows Server Full]`
19
20	3. Windows Server version to use:
21	- `[2022, 2019, or 2016 (Default 2022)]`
22
23	4. Custom base image for the build stage of the Docker image ("None" to use standard Microsoft base image):
24	- `[Specify base image to use for build stage (Default None)]`
25
26	5. Custom base image for the run stage of the Docker image ("None" to use standard Microsoft base image):
27	- `[Specify base image to use for run stage (Default None)]`
28
29	### Container Configuration
30	1. Ports that must be exposed in the container image:
31	- Primary HTTP port: `[e.g., 80]`
32	- Additional ports: `[List any additional ports, or "None"]`
33
34	2. User account the container should run as:
35	- `[User account, or default to "ContainerUser"]`
36
37	3. IIS settings that must be configured in the container image:
38	- `[List any specific IIS settings, or "None"]`
39
40	### Build configuration
41	1. Custom build steps that must be performed before building the container image:
42	- `[List any specific build steps, or "None"]`
43
44	2. Custom build steps that must be performed after building the container image:
45	- `[List any specific build steps, or "None"]`
46
47	### Dependencies
48	1. .NET assemblies that should be registered in the GAC in the container image:
49	- `[Assembly name and version, or "None"]`
50
51	2. MSIs that must be copied to the container image and installed:
52	- `[MSI names and versions, or "None"]`
53
54	3. COM components that must be registered in the container image:
55	- `[COM component names, or "None"]`
56
57	### System Configuration
58	1. Registry keys and values that must be added to the container image:
59	- `[Registry paths and values, or "None"]`
60
61	2. Environment variables that must be set in the container image:
62	- `[Variable names and values, or "Use defaults"]`
63
64	3. Windows Server roles and features that must be installed in the container image:
65	- `[Role/feature names, or "None"]`
66
67	### File System
68	1. Files/directories that need to be copied to the container image:
69	- `[Paths relative to project root, or "None"]`
70	- Target location in container: `[Container paths, or "Not applicable"]`
71
72	2. Files/directories to exclude from containerization:
73	- `[Paths to exclude, or "None"]`
74
75	### .dockerignore Configuration
76	1. Patterns to include in the `.dockerignore` file (.dockerignore will already have common defaults; these are additional patterns):
77	- Additional patterns: `[List any additional patterns, or "None"]`
78
79	### Health Check Configuration
80	1. Health check endpoint:
81	- `[Health check URL path, or "None"]`
82
83	2. Health check interval and timeout:
84	- `[Interval and timeout values, or "Use defaults"]`
85
86	### Additional Instructions
87	1. Other instructions that must be followed to containerize the project:
88	- `[Specific requirements, or "None"]`
89
90	2. Known issues to address:
91	- `[Describe any known issues, or "None"]`
92
93	## Scope
94
95	- ✅ App configuration modification to ensure config builders are used to read app settings and connection strings from the environment variables
96	- ✅ Dockerfile creation and configuration for an ASP.NET application
97	- ✅ Specifying multiple stages in the Dockerfile to build/publish the application and copy the output to the final image
98	- ✅ Configuration of Windows container platform compatibility (Windows Server Core or Full)
99	- ✅ Proper handling of dependencies (GAC assemblies, MSIs, COM components)
100	- ❌ No infrastructure setup (assumed to be handled separately)
101	- ❌ No code changes beyond those required for containerization
102
103	## Execution Process
104
105	1. Review the containerization settings above to understand the containerization requirements
106	2. C

People who liked this also viewed

6 picks

Type

hyperframes-cliUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, SkillsJul 2026262k37k
request-refactor-planSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026165k181k
analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrSkillsMay 2026161k507
explore-codeRigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated braSkillsMay 2026161k507
ubiquitous-languageSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026160k181k
scaffold-exercisesSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026149k181k

containerize-aspnet-framework

8.6kinstalls4.6kforks

View on GitHub

How to install containerize-aspnet-framework?

github/awesome-copilot/containerize-aspnet-framework

$npx -y skills add github/awesome-copilot --skill containerize-aspnet-framework

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# ASP.NET .NET Framework Containerization Prompt
2
3	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.
4
5	REMEMBER: This is a .NET Framework application, not .NET Core. The containerization process will be different from that of a .NET Core application.
6
7	## Containerization Settings
8
9	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.
10
11	Any settings that are not specified will be set to default values. The default values are provided in `[square brackets]`.
12
13	### Basic Project Information
14	1. Project to containerize:
15	- `[ProjectName (provide path to .csproj file)]`
16
17	2. Windows Server SKU to use:
18	- `[Windows Server Core (Default) or Windows Server Full]`
19
20	3. Windows Server version to use:
21	- `[2022, 2019, or 2016 (Default 2022)]`
22
23	4. Custom base image for the build stage of the Docker image ("None" to use standard Microsoft base image):
24	- `[Specify base image to use for build stage (Default None)]`
25
26	5. Custom base image for the run stage of the Docker image ("None" to use standard Microsoft base image):
27	- `[Specify base image to use for run stage (Default None)]`
28
29	### Container Configuration
30	1. Ports that must be exposed in the container image:
31	- Primary HTTP port: `[e.g., 80]`
32	- Additional ports: `[List any additional ports, or "None"]`
33
34	2. User account the container should run as:
35	- `[User account, or default to "ContainerUser"]`
36
37	3. IIS settings that must be configured in the container image:
38	- `[List any specific IIS settings, or "None"]`
39
40	### Build configuration
41	1. Custom build steps that must be performed before building the container image:
42	- `[List any specific build steps, or "None"]`
43
44	2. Custom build steps that must be performed after building the container image:
45	- `[List any specific build steps, or "None"]`
46
47	### Dependencies
48	1. .NET assemblies that should be registered in the GAC in the container image:
49	- `[Assembly name and version, or "None"]`
50
51	2. MSIs that must be copied to the container image and installed:
52	- `[MSI names and versions, or "None"]`
53
54	3. COM components that must be registered in the container image:
55	- `[COM component names, or "None"]`
56
57	### System Configuration
58	1. Registry keys and values that must be added to the container image:
59	- `[Registry paths and values, or "None"]`
60
61	2. Environment variables that must be set in the container image:
62	- `[Variable names and values, or "Use defaults"]`
63
64	3. Windows Server roles and features that must be installed in the container image:
65	- `[Role/feature names, or "None"]`
66
67	### File System
68	1. Files/directories that need to be copied to the container image:
69	- `[Paths relative to project root, or "None"]`
70	- Target location in container: `[Container paths, or "Not applicable"]`
71
72	2. Files/directories to exclude from containerization:
73	- `[Paths to exclude, or "None"]`
74
75	### .dockerignore Configuration
76	1. Patterns to include in the `.dockerignore` file (.dockerignore will already have common defaults; these are additional patterns):
77	- Additional patterns: `[List any additional patterns, or "None"]`
78
79	### Health Check Configuration
80	1. Health check endpoint:
81	- `[Health check URL path, or "None"]`
82
83	2. Health check interval and timeout:
84	- `[Interval and timeout values, or "Use defaults"]`
85
86	### Additional Instructions
87	1. Other instructions that must be followed to containerize the project:
88	- `[Specific requirements, or "None"]`
89
90	2. Known issues to address:
91	- `[Describe any known issues, or "None"]`
92
93	## Scope
94
95	- ✅ App configuration modification to ensure config builders are used to read app settings and connection strings from the environment variables
96	- ✅ Dockerfile creation and configuration for an ASP.NET application
97	- ✅ Specifying multiple stages in the Dockerfile to build/publish the application and copy the output to the final image
98	- ✅ Configuration of Windows container platform compatibility (Windows Server Core or Full)
99	- ✅ Proper handling of dependencies (GAC assemblies, MSIs, COM components)
100	- ❌ No infrastructure setup (assumed to be handled separately)
101	- ❌ No code changes beyond those required for containerization
102
103	## Execution Process
104
105	1. Review the containerization settings above to understand the containerization requirements
106	2. C

People who liked this also viewed

6 picks

Type