Building better DTOs in C#

[@allannielsen4752]

I use records too, but only include mandatory fields in constructor, optional are init properties in the record.

[@gui.ferreira]

Great approach

[@kitsurubami]

Love this video. Thank you!

[@gui.ferreira]

Thank you 🙏

[@christianschulz4475]

I can support all your recommendations. Had an app with generated DTO and few additional methods. And inheritance from a basic DTO. Over the years, this has evolved into DTOs for every use case. Especially the division into request and response DTO has made the code more maintainable.

[@gui.ferreira]

Thanks for sharing!

[@bl1tz229]

Watch out when you have to convert a DTO to a database record using the “id” field. Since the “id” field will try to automatically map towards the id field of the database record, resulting in an InvalidCastException (since often, a database id is defined as integer)

[@thelostrider1]

Hmm. What do you mean, any example?

[@jindhk]

How do we make authentication between those dll calls that will not greatly slow the dll's we are using for dto. Any package suggestion?

[@marcobaccaro]

What kind of question is that? It makes no sense at all.

[@AboutCleanCode]

records are a very convenient and concise way to define data structures but there is no simple way to validate that the parameters passed to the primary constructor are valid. I found some trick recently, but it is not very intuitive so i rarely use it ▶ kzbin.info/www/bejne/fXubl2yobpyMiqM

[@WhichWazzockWantedEmailHandles]

I love how you explained the 'required' keyword, your channel needs more subscribers.

[@richardhaughton9633]

What about readonly computed properties like FullName => $"{FirstName} {LastName}". I often use readonly computed properties which transforms the data iny my Dtos. The other system will just see it as another property. What you think about it?

[@gui.ferreira]

There are some use cases where that approach is useful. Example: retro compatible changes

[@alfonsdeda8912]

Hi, if I don't have all dto parameters in one time, for example in blazor form, should i use two different models, one mutable that stores form datas and One immutable dto that is built from the mutable model?

[@DieDona]

Most likely you are not in need of a dto. Assuming you are on the frontend with blazor, you will need a mutable object to fill in the data. Then, when all your data is ready to be sent over to the backend, create a dto. In short, if you are handling an object, causing mutation, most like it's not a dto.

[@gui.ferreira]

I have no experience with blazor. Isn't it the case of MVVM? Model-view-view-model?

[@alfonsdeda8912]

@@gui.ferreira not exactly, Is component based model

[@gui.ferreira]

@@alfonsdeda8912 On that case, I don't see the object that supports the component as a DTO.

[@alfonsdeda8912]

So i have to create One model to store mutable component data and create before saving the dto, Is correct?

[@codeDotnet]

thanks

[@webbi1540]

Its not a matter of preferrence. Should always be using record for safety today. Thats the problem with c#, so many alternatives which doesn’t good anymore.

[@BloomfieldBlanche]

Moore Kenneth Hall Daniel White Melissa