Mastodawn

The new #testcontainers for #dotnet release has arrived: https://github.com/testcontainers/testcontainers-dotnet/releases/tag/4.11.0. Version 4.11 comes with new modules, bug fixes, and improvements, plus OpenSSF Scorecard analyses for extra trustworthiness. I've also got an update ready for the Docker.DotNet client, which in the next release will bring performance improvements, better resource usage, lots of fixes, and support for .NET's native HTTP handler 💪.

Release 4.11.0 · testcontainers/testcontainers-dotnet

What's Changed Thanks to all contributors. Once again, really great contributions from everyone 🤝. The NuGet packages for this release have been attested for supply chain security using actions/att...

GitHub

Show thread

Andre Hofmeister Feb 27

With the new design and structure, adding or extending handlers is much easier. SSH support is coming soon.

Andre Hofmeister Feb 27

I've started refactoring Docker.DotNet and introducing a more modern, reliable implementation.

Just added a clean builder API for creating Docker client instances. With help from the community, it now supports the .NET native HTTP handlern. No more mandatory legacy, slow implementation (opt-in for now): https://github.com/testcontainers/Docker.DotNet?tab=readme-ov-file#usage. #docker #dotnet

Andre Hofmeister Feb 13

I've put together a few slides for future #testcontainers for #dotnet talks. If you're interested in discussing #testcontainers, let me know. Feedback on the slides is welcome as well: https://andrehofmeister.com/en/testcontainers-for-dotnet.

Testcontainers for .NET

Andre Hofmeister Dec 10

I never expected such an amazing journey when I started working on #testcontainers for #dotnet years ago. I've met many great people and learned a lot. I'm truly grateful for all of it. I never imagined the packages would one day pass 150M+ downloads!

Check out Testcontainers (https://testcontainers.com/) and test against real dependencies with confidence.

Andre Hofmeister Dec 4

Docker.DotNet is now compatible with the latest #docker Engine v29 (https://github.com/testcontainers/Docker.DotNet/releases/tag/v3.131.0). Please note that backward compatibility with earlier API versions is limited due to the project's current structure. I will address this limitation in upcoming releases. #dotnet

Show thread

Andre Hofmeister Nov 24

Thanks again to everyone who contributed :tc-love:

Andre Hofmeister Nov 24

A new #testcontainers for #dotnet release is available. This release supports .NET 10 and ensures compatibility with Docker Engine v29: https://github.com/testcontainers/testcontainers-dotnet/releases/tag/4.9.0. I'm working on updating Docker.DotNet for full v29 support, so expect a new version soon /cc @docker.

Check out the new available modules like Playwright, Grafana, or my favorite this release, Toxiproxy. It's a really interesting tool for pushing testing further: https://dotnet.testcontainers.org/modules/toxiproxy/.

Release 4.9.0 · testcontainers/testcontainers-dotnet

What's Changed This release adds a new configuration (DOCKER_API_VERSION) that lets you pin and downgrade the Docker Engine API version. This was needed because Docker Engine v29 introduced breakin...

GitHub

Show thread

Andre Hofmeister Nov 23

Finally found the issue. I had unintentionally set the debug type in the global property configuration to embedded. Ran into a similar issue to what's described here: https://www.reddit.com/r/Blazor/comments/1p157oc/wasm_debug_not_working_after_upgrade_to_net_100. Looks like .NET 10 behaves differently with Blazor WASM (client-side) than earlier versions. /cc @Pascal

Show thread

Andre Hofmeister Nov 22

Any idea how I can get more details? When I refresh the app in the browser that Rider launches, it shows "Initializing debugger", then fails.

📍	Behind a keyboard or guitar
Website	https://www.andrehofmeister.com
GitHub	https://github.com/HofmeisterAn