<![CDATA[Hannes Karask Blog]]> https://karask.com https://karask.com/uploads/dp.jpg Hannes Karask Blog https://karask.com RSS for Node Sat, 14 Jun 2025 04:42:49 GMT Sat, 14 Jun 2025 04:42:49 GMT <![CDATA[Mocking HTTP calls in ASP.NET Integration Tests]]> (); handlerMock .Protected() .Setup>( "SendAsync", ItExpr.IsAny(), ItExpr.IsAny() ) .ReturnsAsync(new HttpResponseMessage { StatusCode = HttpStatusCode.OK, Content = new StringContent("{\"message\":\"Hello World!\"}") }); var httpClient = new HttpClient(handlerMock.Object) { BaseAddress = new Uri("https://api.example.com/") }; ``` How would you go about doing that in an Integration Testing scenario, where services get wired up by the framework? ASP.NET has a nifty way of hosting your ASP.NET API in memory using the [Microsoft.AspNetCore.Mvc.Testing](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.Testing) package. It takes just a few lines of code to fire up an in-memory API, but mocking the external calls becomes tricky unless you want to replace every single service registration with a custom `HttpClient` + mocked handler combo. There's an easier way: you can register a custom `HttpMessageHandlerBuilder`. ]]> https://karask.com/mocking-http-calls-in-asp-net-integration-tests https://karask.com/mocking-http-calls-in-asp-net-integration-tests Mon, 09 Jun 2025 00:00:00 GMT <![CDATA[GitHub Code Search Cheat Sheet]]> https://karask.com/github-code-search-cheat-sheet https://karask.com/github-code-search-cheat-sheet Mon, 19 Jun 2023 00:00:00 GMT <![CDATA[Generate HTML to PDF using AWS Lambda and Wkhtmltopdf]]> https://karask.com/generate-html-to-pdf-using-aws-lambda-and-wkhtmltopdf https://karask.com/generate-html-to-pdf-using-aws-lambda-and-wkhtmltopdf Sun, 12 Mar 2023 00:00:00 GMT <![CDATA[ASP.NET Core Consistent JSON Problem Details Response]]> https://karask.com/asp-net-core-consistent-json-problem-details https://karask.com/asp-net-core-consistent-json-problem-details Sun, 03 Oct 2021 00:00:00 GMT <![CDATA[Automate Swagger/OpenApi snapshot testing]]> https://karask.com/swagger-openapi-snapshot-testing https://karask.com/swagger-openapi-snapshot-testing Tue, 16 Mar 2021 00:00:00 GMT <![CDATA[AWS CloudFront: Access to script has been blocked by CORS policy' description: 'How to fix the CORS issue with AWS CloudFront: Access to script at x from origin y has been blocked by CORS policy: No Access-Control-Allow-Origin header is present on the requested resource.]]> https://karask.com/fix-the-aws-cloudfront-error-access-to-script-has-been-block https://karask.com/fix-the-aws-cloudfront-error-access-to-script-has-been-block Mon, 08 Feb 2021 00:00:00 GMT <![CDATA[Seed Postgres database with Docker Compose]]> https://karask.com/seed-postgres-database-with-docker-compose https://karask.com/seed-postgres-database-with-docker-compose Thu, 04 Feb 2021 00:00:00 GMT <![CDATA[The new and easy way to debug through NuGet packages with the Source Link]]> https://karask.com/nuget-packages-and-debugging-with-source-link https://karask.com/nuget-packages-and-debugging-with-source-link Tue, 02 Feb 2021 00:00:00 GMT <![CDATA[Retry PowerShell Invoke-WebRequest]]>
PowerShell
Fetching resources over the network isn’t always reliable. Timeouts and other connections issues are quite common, especially if the server is under stress. If you’re okay with the resource being temporarily unavailable, feel free to use the following retry script:
]]> https://karask.com/retry-powershell-invoke-webrequest https://karask.com/retry-powershell-invoke-webrequest Tue, 02 Feb 2021 00:00:00 GMT <![CDATA[Simple ELMAH-like web error logging for ASP.NET Core using MongoDB]]> https://karask.com/simple-elmah-like-web-error-logging-for-aspnet-core https://karask.com/simple-elmah-like-web-error-logging-for-aspnet-core Tue, 02 Feb 2021 00:00:00 GMT <![CDATA[TeamCity Building NuGet Packages]]> https://karask.com/teamcity-building-nuget-packages https://karask.com/teamcity-building-nuget-packages Tue, 02 Feb 2021 00:00:00 GMT