---
name: aspnet-framework-docs
description: Official Microsoft Learn workflow for ASP.NET Framework and .NET Framework 4.x guidance. Use when answering questions about ASP.NET Framework apps (MVC 5, Web API 2, Web Forms), framework installation/version checks, deployment, API reference lookup, or support lifecycle decisions that must stay aligned with Microsoft documentation.
title: aspnet-framework-docs
canonical_url: https://skilld.dev/gh/rscoopcur/aspnet-framework-skills/aspnet-framework-docs
last_updated: 2026-10-08T07:31:36.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-docs/agents/openai.yaml), [references/microsoft-learn-dotnet-framework.md](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-docs/references/microsoft-learn-dotnet-framework.md).
>
> If the user asked to install this Skill, run `npx skilld install rscoopcur/aspnet-framework-skills/aspnet-framework-docs`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/aspnet-framework-docs`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/rscoopcur/aspnet-framework-skills/aspnet-framework-docs) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/aspnet-framework-docs`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/aspnet-framework-docs --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/aspnet-framework-docs --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# ASP.NET Framework Docs

## Overview

Use this skill to produce documentation-grounded answers for legacy ASP.NET Framework and .NET Framework 4.x work. Load `references/microsoft-learn-dotnet-framework.md` and prefer those links as canonical sources.

## Workflow

1. Identify stack and target runtime.
- Confirm whether the user means ASP.NET Framework (System.Web, MVC 5/Web API 2/Web Forms) versus ASP.NET Core.
- Detect target framework from `.csproj`, `packages.config`, or `web.config` when files are available.
- State assumptions explicitly if the target is not provided.

2. Route to the right documentation cluster.
- Use install/version pages for runtime detection, prerequisites, and blocked installation issues.
- Use guide/deployment pages for architecture, configuration, and rollout questions.
- Use support-policy pages for lifecycle and package-support questions.

3. Build response with version and lifecycle context.
- Include concrete version data that affects recommendations (for example .NET Framework 4.8.1 status).
- Use absolute dates for lifecycle statements when available.
- Add direct links to the specific documentation pages used.

4. Produce implementation guidance.
- Start with the smallest safe change for legacy systems.
- Separate short-term maintenance advice from migration advice.
- Keep ASP.NET Core migration suggestions optional unless the user asks for modernization.

## Guardrails

- Avoid mixing ASP.NET Core instructions into ASP.NET Framework implementation steps.
- Re-check lifecycle details on official policy pages for any "latest support" request.
- Prefer Microsoft Learn and official .NET policy pages over blog/community content.

## Reference File

- `references/microsoft-learn-dotnet-framework.md`
  Load this first for link routing, support notes, and recommended search patterns.
