WireMock.Net.Extensions.Routing
1.16.0
Prefix Reserved
dotnet add package WireMock.Net.Extensions.Routing --version 1.16.0
NuGet\Install-Package WireMock.Net.Extensions.Routing -Version 1.16.0
<PackageReference Include="WireMock.Net.Extensions.Routing" Version="1.16.0" />
<PackageVersion Include="WireMock.Net.Extensions.Routing" Version="1.16.0" />
<PackageReference Include="WireMock.Net.Extensions.Routing" />
paket add WireMock.Net.Extensions.Routing --version 1.16.0
#r "nuget: WireMock.Net.Extensions.Routing, 1.16.0"
#:package WireMock.Net.Extensions.Routing@1.16.0
#addin nuget:?package=WireMock.Net.Extensions.Routing&version=1.16.0
#tool nuget:?package=WireMock.Net.Extensions.Routing&version=1.16.0
WireMock.Net
A C# .NET version based on mock4net which mimics functionality from the original Java based WireMock.
📚 Full documentation can now be found at wiremock.org
⭐ 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
📝 Blogs
- mstack.nl : Generate C# Code from Mapping(s)
- mstack.nl : Chaos Engineering with Fault Injections
- mstack.nl : gRPC / ProtoBuf Support
- mstack.nl : Build and test your own .NET Aspire component
💻 Project Info
| Project | |
| Chat | |
| Issues | |
| Quality | |
| Build Azure | |
| Quality | |
| Sonar Bugs | |
| Coverage | |
| TIOBE | TIOBE Quality Indicator |
📦 NuGet packages
| Official | Preview :information_source: | |
|---|---|---|
| WireMock.Net | ||
| WireMock.Net.Minimal 🔺 | ||
| WireMock.Net.StandAlone | ||
| WireMock.Net.Testcontainers | ||
| WireMock.Net.Aspire | ||
| WireMock.Net.AspNetCore.Middleware | ||
| WireMock.Net.AwesomeAssertions | ||
| WireMock.Net.FluentAssertions | ||
| WireMock.Net.xUnit | ||
| WireMock.Net.xUnit.v3 | ||
| WireMock.Net.TUnit | ||
| WireMock.Net.Extensions.Routing | ||
| WireMock.Net.Matchers.CSharpCode | ||
| WireMock.Net.OpenApiParser | ||
| WireMock.Net.MimePart | ||
| WireMock.Net.GraphQL | ||
| WireMock.Net.ProtoBuf | ||
| WireMock.Net.RestClient | ||
| WireMock.Org.RestClient |
<br />
🔺 WireMock.Net.Minimal does not include WireMock.Net.MimePart, WireMock.Net.GraphQL and WireMock.Net.ProtoBuf.
❗ Breaking changes
1.7.0
A breaking change is introduced which is related to System.Linq.Dynamic.Core DynamicLinq (CVE).
- The
LinqMatcheris not allowed. - The Handlebars.Net.Helpers.DynamicLinq package is not included anymore.
1.8.0
Some breaking changes are introduced in this version:
Handlebars.Net File-helper
By default, the internal Handlebars.Net File-helper is not allowed anymore because of potential security issues.
To still enable this feature, you need to set the AllowedCustomHandlebarHelpers property to File in the HandlebarsSettings property in WireMockServerSettings.
Handlebars.Net Environment-helper
By default, the Handlebars.Net Environment-helper is not automatically allowed anymore because of potential security issues.
To still enable this feature, you need to add the Environment category to the AllowedHandlebarsHelpers list-property in the HandlebarsSettings property in WireMockServerSettings.
📝 Development
For the supported frameworks and build information, see this page.
⭐ Stubbing
A core feature of WireMock.Net is the ability to return predefined HTTP responses for requests matching criteria. See Stubbing.
⭐ Request Matching
WireMock.Net support advanced request-matching logic, see Request Matching.
⭐ Response Templating
The response which is returned WireMock.Net can be changed using templating. This is described here Response Templating.
⭐ Admin API Reference
The WireMock admin API provides functionality to define the mappings via a http interface see 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 UnitTesting.
Unit/Integration Testing using Testcontainers.DotNet
See 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 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 dotnet tool.
As standalone process / console application
This is quite straight forward to launch a mock server within a console application, see Standalone Process.
As a Windows Service
You can also run WireMock.Net as a Windows Service, follow this 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 HTTPS
📚 Documentation
For more info, see also this documentation page: What is WireMock.Net.
Powered by
| 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. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net8.0
- JsonConverter.Newtonsoft.Json (>= 0.7.0)
- System.Text.RegularExpressions (>= 4.3.1)
- WireMock.Net.Minimal (>= 1.16.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.16.0 | 361 | 11/18/2025 |
| 1.15.0 | 204 | 10/22/2025 |
| 1.14.0 | 174 | 10/6/2025 |
| 1.14.0-preview-01 | 144 | 10/3/2025 |
| 1.13.0 | 177 | 9/28/2025 |
| 1.12.0 | 473 | 8/30/2025 |
| 1.11.2 | 255 | 8/27/2025 |
| 1.11.1 | 212 | 8/27/2025 |
| 1.11.0 | 234 | 8/26/2025 |
| 1.10.1 | 348 | 8/22/2025 |
| 1.10.0 | 175 | 8/18/2025 |
| 1.10.0-preview-01 | 174 | 8/18/2025 |
# 1.16.0 (18 November 2025)
- #1366 WireMock.Net.OpenApiParser : support Examples [feature]
- #1375 Add WireMockHealthCheck in WireMock.Net.Aspire [feature]
- #1377 Check if the path is valid when using WithPath(...) [feature]
- #1380 Add WireMock.Net.xUnit.v3 project [feature]
- #1364 Choosing examples from open api specification for responses. [feature]
- #1376 AdminApiMappingBuilder `WithPath` should add the starting `/` if missing [feature]
- #1379 xUnit v3 [feature]
The full release notes can be found here: https://github.com/wiremock/WireMock.Net/blob/master/CHANGELOG.md