mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 14:20:29 +01:00
Version 1.11.0 seems to have a dependency to non-existing version of JetBrans.Annotations #714
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HumanPrinter on GitHub (Aug 27, 2025).
Originally assigned to: @StefH on GitHub.
Describe the bug
When running a unit test using WireMock.Net version 1.11.0, a
System.IO.FileNotFoundExceptionis being thrown when callingWireMockServer.Start()The exception message is:
Expected behavior:
WireMockServer.Start()should finish without exception as it did in version 1.10.1Test to reproduce
Other related info
Target framework: .NET 8.0 (but .NET 9.0 gives the same error).
IDE: Visual Studio 2022 (but pipeline in Azure DevOps gives the same error)
@StefH commented on GitHub (Aug 27, 2025):
Seems to be a strange error from JetBrains.Annotations?
See also these links...
https://www.google.com/search?q=JetBrains.Annotations%2C+Version%3D4242.42.42.42
Maybe something with reflection / loading assemblies?
First I'll try to fix any new code which handles loading dll's and loading types, I'll create a new NuGet.
If that does not solve it, I'll revert JetBrains.Annotations.
@StefH commented on GitHub (Aug 27, 2025):
https://github.com/wiremock/WireMock.Net/pull/1352
@StefH commented on GitHub (Aug 27, 2025):
@HumanPrinter
In some time (1 hour max) a new version will be available, can you check that one?
@StefH commented on GitHub (Aug 27, 2025):
https://github.com/wiremock/WireMock.Net/pull/1355
@HumanPrinter commented on GitHub (Aug 27, 2025):
I have tested with the latest version (1.11.1) but the error persists
@StefH commented on GitHub (Aug 27, 2025):
1.11.2 will revert it, I'm building the NuGet now, please wait some time and retry.
@HumanPrinter commented on GitHub (Aug 27, 2025):
I can confirm that version 1.11.2 has fixed the issue. Thanks for the quick response