Csla plus ADO.NET and stored procs #2992
Replies: 3 comments 4 replies
-
I'm using Dapper in a couple of projects. Pretty satisfied. |
Beta Was this translation helpful? Give feedback.
-
I largely code generate mine in new repositories, and then maintain it manually after that. Maintaining it is occasionally problematic, as it is possible to forget when you add a field. It's not perfect, but generally it works OK. I would want to be slightly cautious of anything too automated, as that's the boundary to the database. For example, while I could use nameof() in the generated code, I'm not sure I would. I wouldn't want anyone to break my code by renaming a DTO property, as they may choose not to make the same - potentially breaking - change in the stored procedures or the objects beneath the SPs. |
Beta Was this translation helpful? Give feedback.
-
I'll be offline until Sunday. I'll try to send you something then. If I
remember correctly I am using reflection. I have an ignore attribute for
the few times I don't want a property to be added as a parameter.
…On Fri, Jun 17, 2022, 6:10 PM Chicagoan2016 ***@***.***> wrote:
@saulyt <https://github.com/saulyt> would love to see some sample code,
how could we not write every line like I mentioned in my question?
—
Reply to this email directly, view it on GitHub
<#2992 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLAXO3AGNSH2WIE35TWAA3VPTZULANCNFSM5ZDGW7WQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi,
Fellow members who use ADO.NET and stored procs for data access, what do you use for mapping stored proc's parameters to data transfer objects?
Code like this could be tedious
We have an old(er) project (at least 10 years old) that uses Enterprise library data access block and I could see mapping of data transfer object to stored procs parameters there.
Regards
Beta Was this translation helpful? Give feedback.
All reactions