This question is locked. New answers and comments are not allowed.
OK, I have seen many different posts and help topics around the usages of stored procedues. I have one main goal using the ORM with them - I want to be able to call my custom created procedures with VERY LITTLE coding on my part - certainly less than ADO.NET requires of me.
I have several possible scenarios:
I am coming from a LINQ to SQL framwork where executing a procedure is as simple as:
I have several possible scenarios:
- Stored procedures without no return result
- Stored procedures with a custom return result (does not match shape of an existing entity)
- Stored procedures with a result set that matches an existing entity.
I am coming from a LINQ to SQL framwork where executing a procedure is as simple as:
Dim context As New SOREOTimeAndBillingL2QLDataContextcontext.PayrollPeriodStart(StartDate, EndDate).. blah, blah, blah.I have seen refernces to the ORM API but to be honest if I am going to have to write that muchg code I may as well use what I already kow - ADO.NET.So, my question is - how many of the scenarios I listed above can be *currently* accomplished with the ORM framework using that little code? Are there any near term plans to address the scenarios listed above which are not currently possible without writing as much code as ADO.NET requires to get the job done?