examQuestionCore VS SQLProvider

I use this to distribute exams to my students https://github.com/rtbsoft/examQuestionCore

Have a look at what I've done here: https://github.com/rtbsoft/examQuestionCore . I'm all for the right level of complexity and accessing dbContext in the controller is just fine. I've worked on a project with a DTO layer and an Repository layer and interfaces everywhere and it just ended up that every change required touching multiple files and running automated tools (which sometimes failed on the build server) -- with almost no gain in security or any other metric I could think of. KISS

Here's a project I created for teaching purposes: https://github.com/rtbsoft/examQuestionCore Hope you can learn something by studying this code.

My front end tool of choice is Vue. You can see the combo here: https://github.com/rtbsoft/examQuestionCore and here: https://github.com/rtbsoft/examQuestionVue.

For completeness, there is also the SqlDataProvider, which I only tried out a little years ago, before composibility was baked in. Worth a look.

Have you heard of type providers? https://fsprojects.github.io/SQLProvider/ I think this library might be what you are looking for

Database: SQL or Event Store. If SQL, One of https://fsprojects.github.io/SQLProvider/, https://github.com/Dzoukr/Dapper.FSharp or https://github.com/SQLStreamStore/SQLStreamStore

One of the more popular Type Providers I used is the SQL Provider, but even it has severe limitations when it comes to .NET Core.

There was a wave of popularity in 2017 as well. I used to work on it full time back then, and enjoyed it a lot. The SQLProvider [0] and other type providers like it are super impressive!

[0] https://fsprojects.github.io/SQLProvider/

(1) F# Type Providers still blow my mind.

Strongly typed SQL/XML/CSV/JSON without boilerplate is a massive leap forward, and it's a shame that it hasn't caught on.

https://fsprojects.github.io/SQLProvider/#Example

Like this?

So... I'm a little bit lost here. I must say, I love this language, but documentation is definitely not its greatest strength. I've looked at the SQLProvider documentation and found no information. Then I looked through the repository issues and found a lot of people with similar issues and, even though they should theoretically be solved with version 1.2, I tried doing what ended up working for them, with little luck. I've tried different combinations of library targets and dependencies versions but none worked.

So when I clone a typical open source F# project from GitHub (e.g. SQLProvider, to pick a recent one that I wrestled with), I'm often at a loss how to build and debug the thing. I've figured out that running build.cmd is usually a good place to start, but then what? Can I still open the .sln in Visual Studio and build/debug it there?