Skip to content
Back to search

eShopLite

eShopLite is a set of reference .NET applications implementing an eCommerce site with features like Semantic Search, MCP, Reasoning models and more.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Azure-Samples/eShopLite with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Azure-Samples/eShopLite'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/azure-samples--eshoplite/badge.svg)](/listings/azure-samples--eshoplite)

HTML

<a href="/listings/azure-samples--eshoplite"><img src="/api/listings/azure-samples--eshoplite/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites

- [.NET 10](https://dotnet.microsoft.com/download/dotnet/10.0) - [Docker Desktop](https://www.docker.com/products/docker-desktop/) or [Podman](https://podman.io/) - [Azure Developer CLI (azd)](https://aka.ms/install-azd) (for Azure deployment) - [Git](https://git-scm.com/downloads) - [Aspire CLI](https://aspire.dev) — install with `dotnet tool install -g aspire.cli` (used for setting local secrets via `aspire secret set`)

Installation

1. Clone the repository:

   git clone https://github.com/Azure-Samples/eShopLite.git

1. Navigate to the scenario directory of interest:

   cd eShopLite/scenarios/[scenario-folder]

1. Login to Azure:

```shell azd auth login ```

1. Provision and deploy all the resources:

```shell azd up ```

It will prompt you to provide an `azd` environment name (like "eShopLite"), select a subscription from your Azure account, and select a [location where the necessary models, like gpt-4.1-mini and ADA-002 are available](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=cognitive-services&regions=all), a sample region can be "eastus2".

Quick setup — Azure OpenAI secrets

The script `scripts\Set-AzureOpenAISecrets.ps1` configures all 17 scenarios at once. Run it from the **repo root**:

pwsh .\scripts\Set-AzureOpenAISecrets.ps1

The script interactively prompts for four values:

| Prompt | Parameter set | |--------|---------------| | Azure OpenAI endpoint | `Parameters:AzureOpenAIEndpoint` | | Azure OpenAI API key *(masked)* | `Parameters:AzureOpenAIApiKey` | | Chat deployment name | `Parameters:AzureOpenAIDeploymentName` | | Embeddings deployment name | `Parameters:AzureOpenAIEmbeddingsDeploymentName` |

Use `-DryRun` to preview the commands without executing them:

pwsh .\scripts\Set-AzureOpenAISecrets.ps1 -DryRun

Internally, the script calls the **Aspire CLI** (`aspire secret set`) for each AppHost it discovers. To set a single value manually, use the same command directly:

aspire secret set Parameters:AzureOpenAIEndpoint "https://<your-resource>.openai.azure.com/" \
  --apphost scenarios/01-SemanticSearch/src/eShopAppHost/eShopAppHost.csproj

> **Note:** Scenario-specific extra parameters (e.g., `Parameters:AzureOpenAIRealtimeDeploymentName` in 03-RealtimeAudio, `Parameters:DeepSeekEndpoint` in 05-deepseek, `Parameters:GitHubModelsToken` in 11-GitHubModels) must still be set manually. See each scenario's README for details.

Quickstart

1. Navigate to a specific scenario folder (e.g., `scenarios/01-SemanticSearch/`) 2. Follow the README instructions in that scenario folder 3. Run the solution using `dotnet run` in the appropriate host project folder

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 301 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # eShopLite
  2. [![GitHub license](https://img.shields.io/github/license/azure-samples/eshoplite.svg)](https://github.com/Azure-Samples/eShopLite/blob/main/LICENSE.md)
  3. [![GitHub contributors](https://img.shields.io/github/contributors/azure-samples/eshoplite.svg)](https://github.com/azure-samples/eshoplite/graphs/contributors/)
  4. [![GitHub issues](https://img.shields.io/github/issues/azure-samples/eshoplite.svg)](https://github.com/azure-samples/eshoplite/issues/)
  5. [![GitHub pull-requests](https://img.shields.io/github/issues-pr/azure-samples/eshoplite.svg)](https://github.com/azure-samples/eshoplite/pulls/)
  6. [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com)
  7. [![GitHub watchers](https://img.shields.io/github/watchers/azure-samples/eshoplite.svg?style=social&label=Watch)](https://github.com/Azure-Samples/eShopLite)
  8. [![GitHub forks](https://img.shields.io/github/forks/azure-samples/eshoplite.svg?style=social&label=Fork)](https://github.com/azure-samples/eshoplite/network/)
  9. [![GitHub stars](https://img.shields.io/github/stars/azure-samples/eshoplite.svg?style=social&label=Star)](https://github.com/Azure-Samples/eShopLite)
  10. [![Azure AI Community Discord](https://img.shields.io/badge/Discord-Azure%20AI-5865F2?logo=discord)](https://aka.ms/ai-discord/dotnet)
  11. [![Azure AI Foundry GitHub Discussions](https://img.shields.io/badge/Discussions-Azure%20AI%20Foundry-blueviolet?logo=github&style=for-the-badge)](https://aka.ms/ai-discussions/dotnet)
  12. **eShopLite** is a set of reference .NET applications implementing an eCommerce site with features like Semantic Search, Model Context Protocol (MCP), Reasoning models, vector databases, and more.
  13. > - ☁️ **Scenarios use .NET and Aspire, with a stable .NET 10 baseline and an isolated .NET 11 RC2 scenario for experimental Blazor AI components. See the dependency baseline below for compatibility exceptions.**
  14. > - 🌟 Don't forget to **[star (🌟) this repo](https://docs.github.com/en/get-started/exploring-projects-on-github/saving-repositories-with-stars)** to find it easier later.
  15. > - ➡️ Get your own copy by **[Forking this repo](https://github.com/azure-samples/eshoplite/fork)** and find it next in your own repositories.
  16. > - ❓ **Have a question?** Besides creating [issues](https://github.com/azure-samples/eshoplite/issues) or [pull requests](https://github.com/azure-samples/eshoplite/pulls), the best option for questions is to join the [Azure AI Discord channel](https://discord.com/invite/ByRwuEEgH4), where a team of AI experts can help you.
  17. ## Features
  18. This project framework provides the following features:
  19. - Modern .NET application architecture with Aspire
  20. - Various search capabilities (keyword search, semantic search)
  21. - Integration with multiple AI models (GPT-4o, DeepSeek-R1, etc.)
  22. - Vector database implementations (In Memory, Azure AI Search, Chroma DB and others)
  23. - Real-time audio capabilities
  24. - Model Context Protocol (MCP) server and client implementation
  25. ## eShopLite Scenarios
  26. The project includes several scenarios demonstrating different capabilities:
  27. | Scenario | Description | Key Technologies |
  28. |----------|-------------|-----------------|
  29. | [01 - Semantic Search](./scenarios/01-SemanticSearch/) | A reference .NET application implementing an eCommerce site with Search features using Keyword Search and Semantic Search. | Aspire, OpenAI GPT-4.1-mini, In-memory Vector DB |
  30. | [02 - Azure AI Search](./scenarios/02-AzureAISearch/) | Implements an eCommerce site with Keyword Search using SQL queries and Semantic Search with Vector Database and Azure AI Search. | Azure AI Search, OpenAI Embeddings, SQL Server |
  31. | [03 - Realtime Audio](./scenarios/03-RealtimeAudio/) | Extends the eCommerce site with advanced search features and real-time audio capabilities powered by the GPT-4o Realtime Audio API. | GPT-4o Realtime Audio API, Audio in Blazor, Aspire |
  32. | [04 - Chroma DB](./scenarios/04-chromadb/) | Implements semantic search functionality using Chroma DB, an open-source database designed for AI applications. | Chroma DB, OpenAI Embeddings, .NET SDK |
  33. | [05 - DeepSeek-R1](./scenarios/05-deepseek/) | Demonstrates integration of the DeepSeek-R1 model for enhanced semantic understanding and search capabilities. | DeepSeek-R1, Aspire, Vector Embeddings |
  34. | [06 - Model Context Protocol (MCP)](./scenarios/06-mcp/) | Implements the Model Context Protocol (MCP) for advanced AI interactions with MCP Servers and MCP Clients. | Model Context Protocol, Function Calling, SSE Events |
  35. | [07 - Agents Concurrent](./scenarios/07-AgentsConcurrent/) | Demonstrates concurrent agent orchestration and advanced AI agent collaboration patterns. | Aspire, Multi-Agent Systems, Orchestration |
  36. | [08 - SQL Server 2025](./scenarios/08-Sql2025/) | Demonstrates the use of vector search and vector indexes in the SQL Database Engine | SQL Server 2025, Vector Search, Vector Indexes |
  37. | [09 - Azure App Service](./scenarios/09-AzureAppService/) | Shows how to deploy an Aspire multi-service eCommerce app to Azure App Service, using SQLite for data and integrating AI search. | Azure App Service, Aspire, OpenAI, SQLite |
  38. | [10 - A2A Network](./scenarios/10-A2ANet/) | Demonstrates advanced agent-to-agent (A2A) communication and orchestration patterns in Aspire, including multi-agent collaboration and reasoning. | Aspire, Multi-Agent Systems, A2A Protocol |
  39. | [11 - GitHub Models](./scenarios/11-GitHubModels/) | Local-first AI development using GitHub Models during local runs, with automatic switch to Azure OpenAI when deployed. | Aspire, GitHub Models, Azure OpenAI |
  40. | [12 - Azure Functions](./scenarios/12-AzureFunctions/) | Optional Azure Functions façade for semantic search and an alternate deployment boundary for vector search. | Azure Functions, Aspire, Azure OpenAI |
  41. | [13 - Observability Assistant with Foundry Local](./scenarios/13-ObservabilityAssistantFoundryLocal/) | Summarizes logs, traces, and incidents with a local-first observability assistant. | Aspire, OpenTelemetry, Foundry Local, Microsoft.Extensions.AI |
  42. | [14 - Product Discovery Copilot](./scenarios/14-ProductDiscoveryCopilot/) | Turns search into natural-language product discovery with grounded explanations. | Semantic search, vector search, Microsoft.Extensions.AI |
  43. | [15 - Store Intelligence Report](./scenarios/15-StoreIntelligenceReport/) | Generates daily business and operational store intelligence reports. | App data, telemetry, AI summarization, reports |
  44. | [16 - MCP Store Operations Tools](./scenarios/16-MCPStoreOperationsTools/) | Exposes safe store capabilities as MCP tools for agent use. | MCP, Aspire, app APIs, tool calling |
  45. | [17 - A2A Store Operations Network](./scenarios/17-A2AStoreOperationsNetwork/) | Shows specialized agents collaborating around the store app through A2A. | A2A, Microsoft Agent Framework, hosted agents |
  46. | [18 - Blazor Agentic UI](./scenarios/18-BlazorAgenticUI/) | Experimental streaming shopping assistant with catalog cards and human-approved cart actions. | .NET 11 RC2, Blazor AI components, AG-UI, Microsoft Agent Framework, Aspire |
  47. New to Scenario 18? Start with its [three-step quick start](./scenarios/18-BlazorAgenticUI/README.md),
  48. then explore the [screenshots](./scenarios/18-BlazorAgenticUI/docs/WALKTHROUGH.md) and
  49. [blog-to-code walkthrough](./scenarios/18-BlazorAgenticUI/docs/CODE_WALKTHROUGH.md).
  50. ## Getting Started
  51. ### Prerequisites
  52. - [.NET 10 SDK 10.0.402](https://dotnet.microsoft.com/download/dotnet/10.0), pinned in the root `global.json`
  53. - [Docker Desktop](https://www.docker.com/products/docker-desktop/) or [Podman](https://podman.io/)
  54. - [Azure Developer CLI (azd)](https://aka.ms/install-azd) (for Azure deployment)
  55. - [Git](https://git-scm.com/downloads)
  56. - [Aspire CLI](https://aspire.dev): install with `dotnet tool install -g Aspire.Cli --version 13.6.1` (used for setting local secrets via `aspire secret set`)
  57. ### Dependency baseline
  58. The October 14, 2026 refresh updates the 17 existing scenarios other than `14-MAFDevUI`
  59. to Aspire 13.6.1 and the latest compatible NuGet releases. The root SDK stays on stable
  60. .NET 10; [Scenario 18](./scenarios/18-BlazorAgenticUI/) overrides it with .NET 11 RC2
  61. for the experimental Blazor components. Install both SDKs to work on all scenarios.
  62. The refresh includes Microsoft.Extensions.AI 10.11.0, OpenTelemetry 1.19,
  63. Microsoft Agent Framework 1.24.0, MCP 2.2.0, and A2A 1.0.0-preview3 where used.
  64. Existing prerelease dependencies remain prerelease where no stable replacement provides
  65. the required functionality. MCP SSE transports and A2A text parts have been migrated to
  66. the current APIs rather than merely changing package versions.
  67. Scenarios 08 and 12 deliberately retain the latest EF Core 9 servicing release, 9.0.21:
  68. their `EFCore.SqlServer.VectorSearch` 9.0.0 provider requires that EF major. The other
  69. EF-backed scenarios use 10.0.13. Local `dotnet-ef` tool manifests follow the matching
  70. EF major. Upgrading the SQL vector provider to native EF 10 requires a separate vector
  71. entity/query migration, not mixing EF 9 relational assemblies with EF 10 tests.
  72. Direct PKCS references select patched 10.0.13 instead of vulnerable transitive versions.
  73. The [MAFDevUI scenario](./scenarios/14-MAFDevUI/README.md) subsequently completed its
  74. compatible dependency and API migration after the Azure MCP prerequisite was supplied.
  75. Its build and 27 tests pass, including offline DevUI/Responses integration coverage.
  76. Live validation with both Azure CLI identity and the updated saved API key passed
  77. embeddings, stock tools, streaming workflows, and all three checkout tiers.
  78. Identity-mode orchestrator checks also confirmed no fallback.
  79. Optional Foundry-hosted agents remain unverified. Builds and
  80. existing tests passed for
  81. the other 17 existing scenario solutions (80 existing tests), and Scenario 18 has 29
  82. passing tests. Scenario 18 was also validated locally with SQL Server 2025, real Foundry
  83. embeddings, and `gpt-6-luna` via Responses: streamed catalog cards, cart rejection/approval,
  84. missing product specifications, and restart against existing data. These checks do not
  85. establish cloud deployability or validate every other scenario against real models.
  86. See [CHANGELOG.md](./CHANGELOG.md) for the new scenario, dependency migrations, setup
  87. scripts, and known upgrade boundaries.
  88. ### Start a scenario locally
  89. Each scenario has its own `aspire.config.json`, so Aspire selects that scenario's AppHost
  90. instead of inheriting the repository-root selection:
  91. ```powershell
  92. cd .\scenarios\18-BlazorAgenticUI
  93. aspire start
  94. ```
  95. Use `aspire run` for a foreground session, and `aspire stop` to stop the selected app.
  96. Install the SDK requested by that scenario's nearest `global.json`: .NET 10.0.402 for
  97. stable scenarios, or .NET 11 RC2 for Scenario 18. A .NET 11 installation does not satisfy
  98. the stable .NET 10 pin. AppHost selection does not install SDKs or configure credentials.
  99. To verify every scenario's local selection without starting services:
  100. ```powershell
  101. pwsh .\scripts\Tests\Test-ScenarioAppHosts.ps1
  102. ```
  103. ### Installation
  104. 1. Clone the repository:
  105. ```bash
  106. git clone https://github.com/Azure-Samples/eShopLite.git
  107. ```
  108. 1. Navigate to the scenario directory of interest:
  109. ```bash
  110. cd eShopLite/scenarios/[scenario-folder]
  111. ```
  112. 1. Login to Azure:
  113. ```shell
  114. azd auth login
  115. ```
  116. 1. Provision and deploy all the resources:
  117. ```shell
  118. azd up
  119. ```
  120. It will prompt you to provide an `azd` environment name (like "eShopLite"), select a subscription from your Azure account, and select a [location where the necessary models, like gpt-4.1-mini and ADA-002 are available](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=cognitive-services&regions=all), a sample region can be "eastus2".
  121. ### Shared Microsoft Foundry models and local secrets
  122. Use PowerShell 7 and sign in with `az login`. The new setup script creates or reuses an
  123. `AIServices` account, deploys the common chat and embedding models, then configures local
  124. AppHost user-secrets through the Aspire CLI. Supply your own subscription, resource group,
  125. globally unique account name, and region:
  126. ```powershell
  127. pwsh .\scripts\Initialize-FoundryModels.ps1 `
  128. -SubscriptionId '<subscription-id>' `
  129. -ResourceGroupName 'rg-eshoplite' `
  130. -AccountName '<globally-unique-account-name>' `
  131. -Location 'eastus2' `
  132. -DryRun
  133. ```
  134. Remove `-DryRun` to provision resources and write secrets. This can incur Azure charges.
  135. `-DryRun` and `-WhatIf` make no Azure calls and do not establish model availability.
  136. The default chat model and deployment name are **`gpt-6-luna`**; embeddings use
  137. **`text-embedding-3-small`**. The script resolves model versions from the regional catalog
  138. and checks SKU support and quota before provisioning. It stops if the requested model is
  139. unavailable, with no automatic substitution. Override model/version, deployment name, SKU,
  140. or capacity with the corresponding `-Chat*` and `-Embeddings*` parameters.
  141. It reuses matching deployments and refuses to overwrite conflicting deployments or enable
  142. key authentication on an account that disables it.
  143. This provisions common model dependencies for local development, not every scenario's
  144. infrastructure. SQL/containers remain managed by each AppHost; Azure AI Search, realtime
  145. audio, DeepSeek, GitHub Models, and other specialized dependencies still need their
  146. scenario-specific setup. It does not change model declarations used by `azd up`.
  147. ### Configure secrets for existing deployments
  148. Secret setup requires the SDK selected by each AppHost's nearest `global.json`.
  149. The script checks SDK availability before requesting a key. If using a nonstandard SDK
  150. installation, pass `-DotNetRoot "<SDK installation directory>"`; the override applies
  151. only to child commands. An Aspire exit code 7 can indicate a missing SDK, not an Azure
  152. authentication problem. Scenario 18 specifically requires .NET 11 RC2.
  153. The existing `scripts\Set-AzureOpenAISecrets.ps1` configures secrets only, without creating
  154. Azure resources. It discovers every `eShopAppHost.csproj`, including layouts without `src`,
  155. and automatically includes future scenarios. Scenario 18 (`18-BlazorAgenticUI`) has its own
  156. AppHost and independent user-secrets store, and is included automatically. Directories
  157. without an AppHost are reported as skipped. Run from the **repo root**:
  158. ```powershell
  159. pwsh .\scripts\Set-AzureOpenAISecrets.ps1
  160. ```
  161. The script interactively prompts for four values:
  162. | Prompt | Parameter set |
  163. |--------|---------------|
  164. | Azure OpenAI endpoint | `Parameters:AzureOpenAIEndpoint` |
  165. | Azure OpenAI API key *(masked)* | `Parameters:AzureOpenAIApiKey` |
  166. | Chat deployment name (default `gpt-6-luna`) | `Parameters:AzureOpenAIDeploymentName` |
  167. | Embeddings deployment name (default `text-embedding-3-small`) | `Parameters:AzureOpenAIEmbeddingsDeploymentName` |
  168. Use `-DryRun` to preview the commands without executing them:
  169. ```powershell
  170. pwsh .\scripts\Set-AzureOpenAISecrets.ps1 -DryRun
  171. ```
  172. For a preview without prompts or an API key:
  173. ```powershell
  174. pwsh .\scripts\Set-AzureOpenAISecrets.ps1 `
  175. -Endpoint 'https://<your-resource>.openai.azure.com/' -NonInteractive -DryRun
  176. ```
  177. Non-interactive writes additionally require `-ApiKey` as a `SecureString`, supplied from a
  178. masked prompt or a secure credential source, not a plaintext key in command history.
  179. Local .NET user-secrets are not an encrypted production secret store.
  180. Internally, the script calls the **Aspire CLI** (`aspire secret set`) for each AppHost it discovers. To set a single value manually, use the same command directly:
  181. ```bash
  182. aspire secret set Parameters:AzureOpenAIEndpoint "https://<your-resource>.openai.azure.com/" \
  183. --apphost scenarios/01-SemanticSearch/src/eShopAppHost/eShopAppHost.csproj
  184. ```
  185. > **Note:** Scenario-specific extra parameters (e.g., `Parameters:AzureOpenAIRealtimeDeploymentName` in 03-RealtimeAudio, `Parameters:DeepSeekEndpoint` in 05-deepseek, `Parameters:GitHubModelsToken` in 11-GitHubModels) must still be set manually. See each scenario's README for details.
  186. ### Quickstart
  187. 1. Navigate to a specific scenario folder (e.g., `scenarios/01-SemanticSearch/`)
  188. 2. Follow the README instructions in that scenario folder
  189. 3. Run the solution using `dotnet run` in the appropriate host project folder
  190. ## Demo
  191. To run the demo, follow these steps:
  192. 1. Navigate to the specific scenario folder
  193. 2. Follow the "Run the solution" instructions in that scenario's README
  194. 3. Access the application via the URLs provided in the console output
  195. ## Sample Application
  196. This is the eShopLite Aplication running, performing a **Keyword Search**:
  197. ![eShopLite Aplication running doing search using keyworkd search](./images/05eShopLite-SearchKeyWord.gif)
  198. This is the eShopLite Aplication running, performing a **Semantic Search**:
  199. ![eShopLite Aplication running doing search using keyworkd search](./images/06eShopLite-SearchSemantic.gif)
  200. This is the eShopLite Application running the **Realtime Audio** feature:
  201. ![eShopLite Application running the Realtime Audio feature](./images/07eShopLite-RealtimeAudio.gif)
  202. This is the eShopLite Application using the **DeepSeek-R1 Reasoning Model**:
  203. ![eShopLite Application using the DeepSeek-R1 Reasoning Model](./images/07ReasoningSearch.png)
  204. The Aspire Dashboard to check the running services:
  205. ![Aspire Dashboard to check the running services](./images/15AspireDashboard.png)
  206. The Azure Resource Group with all the deployed services:
  207. ![Azure Resource Group with all the deployed services](./images/10AzureResources.png)
  208. ## Resources
  209. - [Generative AI for Beginners .NET](https://aka.ms/genainet)
  210. - [Aspire Documentation](https://aspire.dev/docs/)
  211. - [Azure OpenAI Service Documentation](https://learn.microsoft.com/azure/ai-services/openai/)
  212. ## Getting Help
  213. If you get stuck or have questions about building AI apps, join:
  214. [![Azure AI Foundry Discord](https://img.shields.io/badge/Discord-Azure_AI_Foundry_Community_Discord-blue?style=for-the-badge&logo=discord&color=5865f2&logoColor=fff)](https://aka.ms/foundry/discord)
  215. If you have product feedback or errors while building, visit:
  216. [![Azure AI Foundry Developer Forum](https://img.shields.io/badge/GitHub-Azure_AI_Foundry_Developer_Forum-blue?style=for-the-badge&logo=github&color=000000&logoColor=fff)](https://aka.ms/foundry/forum)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.