FastEndpoints VS SqlClient

In a recent podcast episode I recorded with Nick Chapsas, we discussed both Minimal API and Mediatr (due to be published on the 1st April). He mentioned a library I hadn't heard of before called Fast Endpoints, which is yet another option. So many different ways to skin a cat. I haven't used Carter, but did use Nancy back in the day.

There's also Fast Endpoints as another way of doing a similar concept (This has API design issues imo, but the concept is solid). It ends up being similar to how a lot of people use MediatR, it's just instead of using controllers you use MapXXX to call MediatR. This just allows people to cut out the MVC overhead.

i believe i've built such a thing. or at least something close to that ;-)

awesome! page looks a bit empty. maybe my rest api framework belongs there too as it's an implementation of REPR pattern https://github.com/dj-nitehawk/FastEndpoints

that's why integration/functional testing with WebApplicationFactory is the way to go.

I will be using Dapper - a simple object mapper for .Net along with Microsoft.Data.Sql.

See the link https://github.com/dotnet/SqlClient/issues/1656

Where I'm having trouble is with this android device connecting to the local sql database at that store. I initially tried connecting directly to the db but ran into this error SQL Server pre-login handshake failed Android 5,6,8.1 · Issue #1656 · dotnet/SqlClient (github.com) - which the only workaround seems to be a dodgy way of turning off security (the DangerousClassProvider class at the bottom of the page). This does actually work but doesn't seem the best way.

I was doing some simple internal tooling with EF. You know the deal, toss in a new row into a table to do something or other, simple CRUD stuff. I was making it in WASM just for the sake of trying out the framework. Turns out this is a thing: https://github.com/dotnet/SqlClient/issues/599 , which prevents EF from running. The wiki page being referenced is gone though, so I don't know the reason why it'd be incompatible. To me it doesn't make that much sense, since a console application would be functionally the same, just outside a browser.

Is any of the columns varchar(max) or similar type? There is a known issue in SqlClient package affecting async reading of such columns.

Code samples for Json.net which as of version 13.0.2 now supports DateOnly and TimeOnly. Three code samples are used to show interactions with Bogus and Microsoft.Data.SqlClient which is most likely used to work with json data.

If you're connecting to SQL Server, connection pooling can be a common cause of apparent memory leaks. If you're opening and closing hundreds of connections, the pool may not be disposing of the connections quickly enough. Or you might be running into issues like this one. You might want to look at SqlConnection.ClearAllPools or SqlConnection.ClearPool or simply disabling connection pooling entirely in the connection string.

Really frustrating to see the amount of effort that went in to gaming those benchmarks when catastrophic performance issues in core Microsoft-authored libraries go unfixed for years. https://github.com/dotnet/SqlClient/issues/593

Until you trip over this https://github.com/dotnet/SqlClient/issues/593