SqlClient VS winforms

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

Windows Forms[0] is still alive and will never die, and very low overhead to start with, and works on new and shiny .NET 8.

If Linux or macOS, you can use AvaloniaUI[1] instead which is sufficiently advanced but assumes some prior knowledge.

[0] https://github.com/dotnet/winforms/blob/main/docs/getting-st...

[1] https://docs.avaloniaui.net/docs/get-started/

Winforms: Licencia MIT.

3. Therefore reified generics are not possible to implement in a backwards compatible way.

Ok, sure, but if you instead a new generic collection types and leave the old ones alone, you don’t have to worry about breaking existing compiled code.

This comment about C# suggests a lack of familiarity with the approach C# took:

> C# made the opposite choice — to update their VM, and invalidate their existing libraries and all the user code that dependend on it.

All of the pre-generic C# libraries continue to exist to this day (ArrayList, HashTable, and the non-generic IEnumerable). Applications that used them never stopped working. New code uses the generic collections (List and Dictionary).

Anyways, I think the costs that Java is currently paying for non-reified generics (reflection, performance, and type safety mentioned in the article) is not worth the backwards comparability with the 20 year old J2SE 1.4. The price C# pays for making a backwards incompatible generics (mostly some minor annoyance when designing a collection class implementing IEnumerable) is worth it at this point.

P.S. ok, I do admit that C# forking the collection library is still causing ongoing maintenance work 18 years later: https://github.com/dotnet/winforms/pull/8673

No, it is fully supported and in active development. https://github.com/dotnet/winforms

No, it's still under active development/maintenance. https://github.com/dotnet/winforms/graphs/contributors

The image is kept in-memory— https://github.com/dotnet/winforms/blob/main/src/System.Windows.Forms/src/System/Windows/Forms/PictureBox.cs

Appears that this has been broken for a while. Seems it has something to do with the new designers being run out of process.

Also, the runtime that C# runs on, is also completely open source as well (https://github.com/dotnet/runtime); ASP.NET which is used to create web apps in C# is open as well (https://github.com/dotnet/aspnetcore). WinForms/WPF, used to make desktop apps in C# is also open source (https://github.com/dotnet/wpf, https://github.com/dotnet/winforms). All of the source code for these are on the dotnet Github page: https://github.com/dotnet and most are all MIT-licensed.

You'll likely have to open an issue against https://github.com/dotnet/winforms. If you've already opened an issue here, then feel free to link and I might be able to provide suggestions on how to improve the triage process.