repowisedotnet-architecture/eshoponweb

dotnet-architecture / eshoponweb

Sample ASP.NET Core 8.0 reference application, now community supported: https://github.com/NimblePros/eShopOnWeb

C#★ 10,680
Use in your agentAsk this codebase

github.com/dotnet-architecture/eshoponwebIndexed at 4da8212Up to date with upstream

What is eshoponweb?

eshoponweb is a sample ASP.NET Core reference application for demonstrating web application architecture and deployment patterns. It uses a single-process monolithic design and focuses on traditional web application development. The main implementation language is C# on ASP.NET Core 8.0.

Written by a model from the README and the source

280 files and 1,451 symbols in 2 modules, led by C# (248 files) and Dockerfile (2).

Start reading

Code health

9.5out of 10Excellent

This codebase scores 9.5 out of 10 for code health, which we rate excellent.

Full health report

Use dotnet-architecture/eshoponweb in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

  1. 1.In Claude, open Customize → Connectors, click +, then Add custom connector. On a Team or Enterprise plan an owner adds it first under Organization settings → Connectors.
  2. 2.Paste the server URL below as the Remote MCP server URL, then click Add.
  3. 3.Click Connect. A Repowise sign-in window opens. Approve access.
  4. 4.Repowise's tools are now available in your Claude chats.

Connect with one click. Sign in with Repowise (OAuth), no API key to copy. Works in Claude on the web, desktop, and mobile.

Docs
bash
https://api.repowise.dev/mcp/dotnet-architecture/eshoponweb
Editors need an API key: sign in to create one.Sign in to connect

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is eshoponweb put together?")
  • get_why("why is eshoponweb structured this way?")

Explore eshoponweb

Key features of eshoponweb

  • eshoponweb demonstrates a single-process monolithic application architecture and deployment model.
  • eshoponweb demonstrates principles and patterns for modern web applications with ASP.NET Core.
  • eshoponweb supports a store catalog and shopping cart data through its database configuration.
  • eshoponweb includes an Admin page implemented with Blazor WebAssembly and a PublicApi web application.
  • eshoponweb can run locally, in Docker, or through an Azure Developer CLI deployment template.

How dotnet-architecture/eshoponweb works

The application runs as a single-process web application with separate supporting projects for public API access and infrastructure concerns. The Web project accepts browser requests and provides the store interface. The PublicApi project supports the Admin page's Blazor WebAssembly client, which communicates with the server through the public API. The Infrastructure directory contains database-related implementation used by the application. The tests directory holds automated tests for the application. Entity Framework Core migrations create separate databases for catalog and shopping cart data and for user credentials and identity data.

The codebase has 280 files and 1,451 symbols in 2 modules, led by C#, Dockerfile and JavaScript. Code health is 9.5 out of 10, rated excellent.

Getting started with eshoponweb

  1. Authenticate with Azure Developer CLI.
    azd auth login
  2. Initialize the application environment.
    azd init -t dotnet-architecture/eShopOnWeb
  3. Provision Azure resources and deploy the application.
    azd up

Commands copied from the README

dotnet-architecture/eshoponweb FAQ

What is eshoponweb?

eshoponweb is a sample ASP.NET Core reference application for demonstrating web application architecture and deployment patterns. It uses a single-process monolithic design.

How does eshoponweb work?

eshoponweb serves a traditional web application through the Web project and supports its Admin page through Blazor WebAssembly and PublicApi. Infrastructure handles database-related implementation, with Entity Framework Core migrations setting up application data stores.

How do I install eshoponweb?

eshoponweb can be initialized and deployed with Azure Developer CLI by running azd auth login, azd init -t dotnet-architecture/eShopOnWeb, and azd up. Local use requires database setup and Entity Framework Core migrations.

What language is eshoponweb written in?

eshoponweb is written primarily in C# and uses ASP.NET Core 8.0. The repository also includes Dockerfile and JavaScript files.

How is the eshoponweb code organized?

eshoponweb is organized mainly under src and tests. The Web project provides the application interface, PublicApi supports the Admin client, and Infrastructure contains database-related code.

When should I use eshoponweb?

eshoponweb is intended for learning and demonstrating web application principles and patterns with ASP.NET Core. It is not intended to implement every feature of a real eCommerce application.

What license does eshoponweb use?

eshoponweb uses the MIT license.

The summary, features and answers on this page are written by a model from the README and the source, and refreshed with each index.

About this page

Get a page like this for your own codebase

Repowise built this map of dotnet-architecture/eshoponweb from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Index your repo freeSee how Repowise worksFree for 2 public repos, with a page like this one.

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.