Hi All.
You will have to excuse me if this question is a bit confusing, but I have only been learning the ASP.NET MVC technology just this week.
I have used Flask and Django before and have this week been playing around with ASP.NET and have been following tutorials that setup an ASP.NET Core Web App. It all seems quite straight forward, and I am able to join the dots and I am sure I could get a competent looking website up and running in a few days.
However, as you will all know, Entity framework is a big part of this and features in pretty much every tutorial. This is fine; however, my place of work has asked me not to use Entity Framework and to use SQL as that is what the other apps here use and so you have a whole team very skilled in SQL. Therefore, they are keen for me to use a technology that the whole team know and can support. The use of Entity framework is a red line.
I like the MVC approach, and I have googled this over the past few days and there is not much around that I can find on directly using ASP.NET with SQL commands to get to and from the database. The only one I did find is this one: https://www.youtube.com/watch?v=T-e554Zt3n4&t=130s
My knowledge is limited, However in this tutorial the presenter did not seem use any of the MVC framework for the functionality, instead choosing to construct the functionality for all pages within the C# behind each page. I have followed this in a fashion but have implemented good practices like moving the DB connectivity to a shared function.
However, having learnt a bit more about ASP.NET CORE MVC In the meantime, I was wondering whether the MVC ASP.NET approach could be followed without using Entity framework? Is there any best/accepted practices or industry standards with this approach? Or is entity framework baked in? If so, what is the best approach to developing an ASP.NET web app when constrained to using SQL?