WireMock.Net.AspNetCore.Middleware
1.8.0
Prefix Reserved
dotnet add package WireMock.Net.AspNetCore.Middleware --version 1.8.0
NuGet\Install-Package WireMock.Net.AspNetCore.Middleware -Version 1.8.0
<PackageReference Include="WireMock.Net.AspNetCore.Middleware" Version="1.8.0" />
<PackageVersion Include="WireMock.Net.AspNetCore.Middleware" Version="1.8.0" />
<PackageReference Include="WireMock.Net.AspNetCore.Middleware" />
paket add WireMock.Net.AspNetCore.Middleware --version 1.8.0
#r "nuget: WireMock.Net.AspNetCore.Middleware, 1.8.0"
#addin nuget:?package=WireMock.Net.AspNetCore.Middleware&version=1.8.0
#tool nuget:?package=WireMock.Net.AspNetCore.Middleware&version=1.8.0
WireMock.Net
Lightweight Http Mocking Server for .NET, inspired by WireMock.org (from the Java landscape).
⭐ Key Features
- HTTP response stubbing, matchable on URL/Path, headers, cookies and body content patterns
- Library can be used in unit tests and integration tests
- Runs as a standalone process, as windows service, as Azure/IIS or as docker
- Configurable via a fluent C# .NET API, JSON files and JSON over HTTP
- Record/playback of stubs (proxying)
- Per-request conditional proxying
- Stateful behaviour simulation
- Response templating / transformation using Handlebars and extensions
- Can be used locally or in CI/CD scenarios
- Can be used for Aspire Distributed Application testing
⭐ Stubbing
A core feature of WireMock.Net is the ability to return predefined HTTP responses for requests matching criteria. See Wiki : Stubbing.
⭐ Request Matching
WireMock.Net support advanced request-matching logic, see Wiki : Request Matching.
⭐ Response Templating
The response which is returned WireMock.Net can be changed using templating. This is described here Wiki : Response Templating.
⭐ Admin API Reference
The WireMock admin API provides functionality to define the mappings via a http interface see Wiki : Admin API Reference.
⭐ Using
WireMock.Net can be used in several ways:
UnitTesting
You can use your favorite test framework and use WireMock within your tests, see Wiki : UnitTesting.
Unit/Integration Testing using Testcontainers.DotNet
See Wiki : WireMock.Net.Testcontainers on how to build a WireMock.Net Docker container which can be used in Unit/Integration testing.
Unit/Integration Testing using an an Aspire Distributed Application
See Wiki : WireMock.Net.Aspire on how to use WireMock.Net as an Aspire Hosted application to do Unit/Integration testing.
As a dotnet tool
It's simple to install WireMock.Net as (global) dotnet tool, see Wiki : dotnet tool.
As standalone process / console application
This is quite straight forward to launch a mock server within a console application, see Wiki : Standalone Process.
As a Windows Service
You can also run WireMock.Net as a Windows Service, follow this WireMock-as-a-Windows-Service.
As a Web Job in Azure or application in IIS
See this link WireMock-as-a-(Azure)-Web-App
In a docker container
There is also a Linux and Windows-Nano container available at hub.docker.com. For more details see also Docker.
HTTPS / SSL
More details on using HTTPS (SSL) can be found here Wiki : HTTPS
📚 Documentation
For more info, see also this WIKI page: What is WireMock.Net.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. |
-
net8.0
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 8.0.0)
- System.Text.RegularExpressions (>= 4.3.1)
- WireMock.Net (>= 1.8.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.8.0 | 42 | 4/29/2025 |
1.8.0-prview-01 | 193 | 3/4/2025 |
1.7.5-preview-02 | 150 | 4/3/2025 |
1.7.5-preview-01 | 143 | 4/2/2025 |
1.7.4 | 521 | 2/27/2025 |
1.7.3 | 96 | 2/24/2025 |
1.7.2 | 104 | 2/12/2025 |
1.7.2-preview-01 | 90 | 2/7/2025 |
1.7.1 | 476 | 1/27/2025 |
1.7.0 | 96 | 1/22/2025 |
1.6.12 | 99 | 1/21/2025 |
1.6.11 | 116 | 1/2/2025 |
1.6.10 | 117 | 12/15/2024 |
1.6.9 | 114 | 12/6/2024 |
1.6.8 | 102 | 11/24/2024 |
1.6.7 | 113 | 10/17/2024 |
1.6.7-preview-02 | 95 | 10/6/2024 |
1.6.7-preview-01 | 94 | 10/2/2024 |
1.6.6 | 111 | 10/1/2024 |
1.6.5 | 102 | 9/28/2024 |
1.6.4-preview-01 | 86 | 9/28/2024 |
# 1.8.0 (28 April 2025)
- #1268 1.7.x [bug]
- #1271 Add HandlebarsSettings [feature]
- #1273 feat(awesome-assertions): Added new project WireMock.Net.AwesomeAssertions [feature]
- #1278 changed null check in JSONPathMatcher and JmesPathMatcher to ensure t… [bug]
- #1283 Add an launch inspector command to Aspire Dashboard [feature]
- #1285 Enable support for WireMock Middleware in Hosted Services [bug]
- #1243 Support for AwesomeAssertions [feature]
- #1264 OpenApiParser - Construction of path possibly incorrect [bug]
- #1275 WithMappingFromOpenApiFile - Support for OpenAPI 3.1.0 [feature]
- #1276 Add WireMock Inspector command to Aspire integration [feature]
- #1277 Newtonsoft.Json.JsonReaderException: 'Unable to read the JSON string.' when using IStringMatcher with an empty body [bug]
- #1284 WireMock.Net.AspNetCore.Middleware does not work in hosted services [bug]
The full release notes can be found here: https://github.com/WireMock-Net/WireMock.Net/blob/master/CHANGELOG.md