Nice idea !

[StefH]

Hello @fredimachado,

I had the same idea : building a WireMock.Net Aspire implementation.
I did also start on this here:
WireMock-Net/WireMock.Net#1109

Your idea of using the MappingBuildder is very interesting! I did copy your idea for this and added it also to the wip PR.

[fredimachado]

Hey @StefH , that's awesome!

I had a quick look at your implementation just now, and I notice mine is super simplistic compared to yours.
I'm looking forward to trying your package as soon as it's available.

Nice profile pic btw. I finally had some time to practice cubing this year, and I managed to solve it. It took months, but I'm already able to solve it in about 1 minute. Not sure if that's super good, specially because I don't plan to break any records, but it's a really nice feeling to be able to solve it.

[StefH]

I've uploaded this NuGet just now: WireMock.Net.Aspire 0.0.1-preview-02 which includes all the code from the current state of the PR.

You can try it.

[StefH]

BTW I noticed that the hooks are executed after a bit of delay.

Do you know if it's possible in Aspire to "wait" until the wiremock.net server has fully started?
Just like it's possible with TestContainers: https://github.com/WireMock-Net/WireMock.Net/blob/master/src/WireMock.Net.Testcontainers/WireMockContainerBuilder.cs#L160

[fredimachado]

You might be able to solve this with Aspirant package. There is a WaitFor extension method that you can use put in any resource that needs to wait for the WireMock container to be running and ready.
https://github.com/aspirant-project/aspirant/blob/main/src/Aspirant.Hosting/WaitForDependencies/WaitForDependenciesExtensions.cs

Here's how I used it: https://github.com/fredimachado/NCafe/blob/main/src/Aspire/NCafe.AppHost/Program.cs

You might have to implement a Health Check, because Aspirant uses it for the WaitFor.

[StefH]

Did you have time to try that preview version?

[StefH]

@fredimachado
I solved it at this moment by waiting on the availability from the /__admin/health endpoint. Latest preview 5 should fix this.