---
name: aspnet-framework-frontend
description: Expert workflow for ASP.NET Framework (.NET Framework 4.x) web apps using Vue 2, Vue 3, or Alpine.js with Razor and Web API. Use when integrating frontend frameworks into ASP.NET Framework, choosing framework patterns, implementing API and anti-forgery flows, troubleshooting runtime/version setup, or answering support and lifecycle questions with official Microsoft Learn .NET Framework documentation.
title: aspnet-framework-frontend
canonical_url: https://skilld.dev/gh/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend
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-frontend/agents/openai.yaml), [references/alpinejs-best-practices.md](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend/references/alpinejs-best-practices.md), [references/aspnet-integration.md](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend/references/aspnet-integration.md), [references/microsoft-learn-dotnet-framework.md](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend/references/microsoft-learn-dotnet-framework.md), [references/vue2-best-practices.md](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend/references/vue2-best-practices.md), [references/vue3-best-practices.md](https://skilld.dev/api/skills-raw/rscoopcur/aspnet-framework-skills/aspnet-framework-frontend/references/vue3-best-practices.md).
>
> If the user asked to install this Skill, run `npx skilld install rscoopcur/aspnet-framework-skills/aspnet-framework-frontend`. 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-frontend`, 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-frontend) 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-frontend`. 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-frontend --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/aspnet-framework-frontend --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 Frontend

## Overview

Use this skill for ASP.NET Framework frontend architecture and implementation. Keep framework-specific code guidance in sync with official Microsoft Learn documentation before giving final recommendations.

## Core Workflow

1. Identify stack and runtime.
- Confirm ASP.NET Framework (MVC 5, Web API 2, Web Forms, System.Web) versus ASP.NET Core.
- Detect target runtime from `.csproj`, `packages.config`, or `web.config`.
- State assumptions when the runtime is unknown.

2. Choose frontend strategy.
- Choose Vue 2 for legacy maintenance and Options API continuity.
- Choose Vue 3 for new/expanded client-side features and composables.
- Choose Alpine.js for lightweight progressive enhancement in server-rendered pages.
- Use Vue + Alpine only with strict root-element isolation.

3. Implement ASP.NET integration path.
- Define bundles in `BundleConfig.cs` and toggle optimization by environment.
- Pass server data to client using strongly typed models or serialized payloads.
- Use Web API endpoints with anti-forgery validation on state-changing requests.
- Centralize fetch helpers and error handling in shared JavaScript utilities.

4. Validate against official documentation.
- Load `references/microsoft-learn-dotnet-framework.md` for install/version/support questions.
- Confirm lifecycle and support answers against policy pages before finalizing.
- Use absolute dates when reporting end-of-support milestones.

5. Deliver response.
- Provide minimal safe implementation steps first.
- Separate maintenance guidance from optional migration guidance.
- Add direct documentation links used for the recommendation.

## Guardrails

- Do not mix ASP.NET Core implementation details into ASP.NET Framework instructions.
- Do not use `v-html` or `x-html` for untrusted input.
- Do not omit anti-forgery token handling for `POST`, `PUT`, or `DELETE`.
- Do not recommend Vue 2 for new greenfield work unless constraints require it.

## Reference Loading Order

1. `references/aspnet-integration.md`
- Use for ASP.NET MVC/Web API + frontend integration structure.

2. Framework-specific reference
- `references/vue2-best-practices.md`
- `references/vue3-best-practices.md`
- `references/alpinejs-best-practices.md`

3. Official documentation map
- `references/microsoft-learn-dotnet-framework.md`
- Use for runtime versions, installation, API browser, and lifecycle policy routing.

## Quick Checklist

- Confirm runtime target (.NET Framework 4.x variant).
- Select Vue 2, Vue 3, or Alpine with explicit rationale.
- Implement bundle strategy and server-to-client data transfer.
- Include anti-forgery flow in API calls.
- Verify support/lifecycle answers with official policy links.
