The EntitySpaces Community

Share and learn about the EntitySpaces Architecture.
Welcome to The EntitySpaces Community Sign in | Join | Help
in
Home Forums Photos

Research EntitySpaces vs LINQ to SQL

Last post 08-29-2008, 9:38 AM by iVirtualDocket. 6 replies.
Sort Posts: Previous Next
  •  08-28-2008, 3:29 AM 10996

    Research EntitySpaces vs LINQ to SQL

    Hello,

    I've been busy doing research for a ORM 1,5 week now and I discovered EntitySpaces. I am very excited about this product, tested a lot and now I would like to ask some additional questions.

    Currently we're working on a huge project which uses the LINQ to SQL technique. Since we're looking on making the development go faster we want to use EntitySpaces but can anyone just tell me the difference/advantages on LINQ to SQL? I have to make it very clear in my research to convince everybody to use ES. I already read about in in the LINQ section but it wasn't very clear to me. Thanks in advance

     With kind regards,

     Johan

     

  •  08-28-2008, 4:12 AM 10999 in reply to 10996

    Re: Research EntitySpaces vs LINQ to SQL

    Well, this is a big topic, I'm about to run out and will provide more info but let me get your started. We do support LINQ to SQL for SQL server, see this POST and this POST.

    However, we also have our own easier to read and understand DynamicQuery API some examples can be found HERE.


     

     


    EntitySpaces | Twitter | BLOG | Please honor our Software License
  •  08-28-2008, 6:49 AM 11009 in reply to 10999

    Re: Research EntitySpaces vs LINQ to SQL

    Okay, thank you in advance. Another question that isn't answered by reading the forum / site is if there is a possibility to automatic generate business rules with Entity Spaces. And the last question.. Could you give me an indication (percentual) how much more efficiëncy and faster a developer can work using the EntitySpaces framework?

    Kind regards,

    Johan

  •  08-28-2008, 7:37 AM 11010 in reply to 11009

    Re: Research EntitySpaces vs LINQ to SQL

    Well, we don't really generate business rules but we do offer the ability to generate a fully hierarchical data model from your database schema which is connected from top to bottom and bottom to top.

    As to how much faster is development here's what I say. Suppose you have 200 tables in your database. I could walk into your shop right now and generate your entire EntitySpaces system in less than 20 minutes, that includes installing MyGeneration and EntitySpaces. Now, you're ready to write your app. You have very good transaction support, strongly typed entities, a very cool intellisense driven DynamicQuery API, good binding support, and a ton of other features at your disposal. You then write code like this:

    Employees emp = new Employees();
    emp.FirstName = "Mike";
    emp.Save();

    No SqlClient, no messy complicated code. And if when you change your database schema, just regenerate in 5 minutes and recompile, it's that simple.

    So, you take all this time savings and pour it into your UI or other areas, you create a much better app in record time. I'm biased of course, but I cannot imagin a faster way to work. EntitySpaces removes all of the grunt work and makes your project fun. Then, when your next project comes along no need to invent another architecture, just use ES again. If a client comes to you and says "We use Oracle can you do that". You say "Yes" because your ES code wont change, same API, same everything.

     


    EntitySpaces | Twitter | BLOG | Please honor our Software License
  •  08-28-2008, 11:23 AM 11013 in reply to 11010

    Re: Research EntitySpaces vs LINQ to SQL

    EntitySpaces is a huge time saver.  I support several Cache databases and load data to SQL Server for data warehousing.  today, 2 lookup tables were added to the Cache ODBC definition.  It took me no more than 20 minutes to:

     1) Create SQL Tables

    2) Generate Custom and Generated classes  for ES using MyGen

    3) Add code to my data loader to load the table

     

    On another table, a column was added today.  So:

    1) add column to SQL Server table

    2) Generate Custom and Generated classes  for ES using MyGen

    3) Update code to extract the extra column from cache and add one line of code to the load piece to populate that field.

    Literally took less than 5 minutes.

     

     

     


  •  08-28-2008, 11:37 PM 11028 in reply to 11013

    Re: Research EntitySpaces vs LINQ to SQL

    Thank you for the quick responses. I have added these result to my research. Looks very promising.

    Kind regards,

    Johan

  •  08-29-2008, 9:38 AM 11036 in reply to 11028

    Re: Research EntitySpaces vs LINQ to SQL

    If you want some actual times, my iVirtualDocket project was first written in pure ADO.Net and it took around 2 months. With ES I managed to write the same application from scratch (with more features) in 3 weeks.

    Current Projects:
    iVirtualDocket | iWontRemember
View as RSS news feed in XML