5 thoughts on “Iowa .NET User Group – 10 Opinions For More Maintainable .NET Apps”
Great article, Scott! Thank you so much for sharing. Do you happen to record any of your presentations? I feel I can learn a lot listening to your explanations on slides rather than going through the slides 🙂
Hi Raj – unfortunately, this talk was not recorded. I try to leave the slides detailed enough where you can get the gist of what I’m saying, so I hope that helps enough!
Your presentation is full of wonderful advice, Scott! I got two ideas out of it – the feature folder structure suggestion and the ORM suggestion. I’d love to learn how to get coworkers partial to ADO comfortable with an ORM, and separately getting coworkers familiar with Dapper familiar with EF. Do you have any thoughts on that?
I think if they’re partial to ADO, I’d get them started with Dapper first. Dapper is the closest to ADO and really just takes care of a lot of the boilerplate with regards to connection management and mapping DataTables/DataSets/etc to Objects.
As far as getting them familiar with Dapper AND EF… I use both depending on the job. An idea might be to write the same code in EF and Dapper and then come together as a team to compare the approaches to see which one you prefer and why. Also comparing them from a testability perspective as well.
Great article, Scott! Thank you so much for sharing. Do you happen to record any of your presentations? I feel I can learn a lot listening to your explanations on slides rather than going through the slides 🙂
Hi Raj – unfortunately, this talk was not recorded. I try to leave the slides detailed enough where you can get the gist of what I’m saying, so I hope that helps enough!
Your presentation is full of wonderful advice, Scott! I got two ideas out of it – the feature folder structure suggestion and the ORM suggestion. I’d love to learn how to get coworkers partial to ADO comfortable with an ORM, and separately getting coworkers familiar with Dapper familiar with EF. Do you have any thoughts on that?
Glad it was useful Cliffie!
I think if they’re partial to ADO, I’d get them started with Dapper first. Dapper is the closest to ADO and really just takes care of a lot of the boilerplate with regards to connection management and mapping DataTables/DataSets/etc to Objects.
As far as getting them familiar with Dapper AND EF… I use both depending on the job. An idea might be to write the same code in EF and Dapper and then come together as a team to compare the approaches to see which one you prefer and why. Also comparing them from a testability perspective as well.
Hope that helps!
omg you reply so quickly. Thanks a ton for the extra advice, Scott!