 |
|
| FriendFeed is the easiest way to share online. Learn more » |
@joshuamck bad for understanding == slowdown. the point is to go faster, right?
thinking about creating an automappercontrib project - not for use in projects as a library, but a code snippet / example repository
nerddinner's viewmodelprofile: http://gist.github.com/140174
i wouldnt use automapper in nerddinner - it's just too small. but if it grew beyond two entities, would be definitely useful
nerddinner has very few screens, so removing larger duplication isn't really an issue.
then that method can be automapped to a dto property (and tested)
but even simpler changes to the domain model have resulted in greater gains. instead of checking the length of a collection in the view,
2: removing method calls on model objects from the view into value resolvers. 3. string casting 4. date time formatting cod
so far, in nerddinner, i have used automapper to the following purposes: removing from the view duplicative prerendering like html encoding
@dagda1 what might help is how we conventionally map those operations.. stuff like this: http://gist.github.com/140166
automapper is best suited for object orientation and the "inversion of control lifestyle"
it worked really well. but for a teeny small project like nerddinner it may be overkill.
took @shanselman 's suggestion and used automapper in nerddinner.
Other ways to read this feed:
