Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As you are working in medium size project, I would suggest you to use LINQ-TO-SQL because of these advantages</p> <p><strong>Advantages using LINQ to SQL:</strong> </p> <p>•No magic strings, like you have in SQL queries •Intellisense •Compile check when database changes •Faster development •Unit of work pattern (context) •Auto-generated domain objects that are usable small projects •Lazy loading. •Learning to write linq queries/lambdas is a must learn for .NET developers. Regarding performance:</p> <p>•Most likely the performance is not going to be a problem in most solutions. To pre-optimize is an anti-pattern. If you later see that some areas of the application are to slow, you can analyze these parts, and in some cases even swap some linq queries with stored procedures or ADO.NET. •In many cases the lazy loading feature can speed up performance, or at least simplify the code a lot. Regarding debuging:</p> <p>•In my opinion debuging Linq2Sql is much easier than both stored procedures and ADO.NET. I recommend that you take a look at Linq2Sql Debug Visualizer, which enables you to see the query, and even trigger an execute to see the result when debugging. •You can also configure the context to write all sql queries to the console window, more information here Regarding another layer:</p> <p>•Linq2Sql can be seen as another layer, but it is a purely data access layer. Stored procedures is also another layer of code, and I have seen many cases where part of the business logic has been implemented into stored procedures. This is much worse in my opinion because you are then splitting the business layer into two places, and it will be harder for developers to get a clear view of the business domain. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload