2
It is valid the development without ORM, because today I want to develop an ERP, but I have no knowledge in any framework, is it valid I do everything in hand? I will have the same result?
Because I realize that I’m wasting a lot of development time to understand how the Entity works, and when there’s a problem I feel I can’t solve alone.
Incidentally in the performance issue only using pure SQL, it is more viable than an ORM?
2
It is valid yes, there are many people who do without a ORM or using a simplified ORM like the Dapper. And that’s what you can objectively answer.
It has several advantages in doing so, it has some disadvantages too, but I will say one thing that is just my opinion: most projects do not need an ORM, or at least there are few that have great benefits.
A good part of the gain of the ORM has to do with the way it develops, as kind of architecture and design who adopts.
It is obvious that without using a few things that are ready you will have to do in hand. If you know how to do well it can be a good one because you are more adapted to your need and you will understand well how everything works. Of course you run the risk of making one Frankestein, can generate excessive work, little flexibility, ease of maintenance, etc. There goes the quality of who is doing. If you do well and can reuse in other projects can compensate since learning EF is really not simple.
What’s good for you no one can answer. You will spend time in any case. A simple ORM or direct access has other advantages. It is true that many of them are not needed in most projects. It’s practically a decision of what problem you want to deal with.
Ironically, less experienced developers tend to get along better with ORM since it delivers a lot of ready-made stuff that only an experienced developer can do without ORM.
The truth is, it’s only with experience that you can make an appropriate decision.
Browser other questions tagged c# sql entity-framework orm erp
You are not signed in. Login or sign up in order to post.
Dude, I think you’ll have to use ADO.NET, where you can make procedures or manual code calls. However, maintenance can be more difficult. I believe that the effort to learn a little about the Entity Framework will be less than with maintenance and with the development of manual code.
– Wilson Santos
Did the answer solve your question? Do you think you can accept it? See [tour] if you don’t know how you do it. This would help a lot to indicate that the solution was useful to you. You can also vote on any question or answer you find useful on the entire site.
– Maniero