Steve Dunn

Apologies, I must've missed this issue. Making `Value` settable violates the immutable aspect of value objects. There are defaultable 'instances' that you can create, please see: https://github.com/SteveDunn/Vogen/wiki/Instances

Thank you again for your PR. I think this is a very interesting concept. However, in its current form, I think we would end up with assemblies with dozens/hundreds of...

@squideyes - sorry for the very slow follow-up. Thank you for the kind words re. this work, much appreciated. Did the recommendations in the README help at all?

Excellent, thank you for spreading the word!

@arteny - I just skimmed through this thread, not bothering to read the comments above yours. I created a 4.7.1 app, and Vogen wasn't recognised. I'd completely forgot about the...

Hi - sorry about the missing documentation. I personally don't do anything that requires EF. The times I do need to read from infrastructure and convert to domain objects, I...

Hi @glen-84 , the name 'anti-corruption layer' sounds complicated, but it essentially means 'map types from one layer to another'. My flow is something like: ```csharp Infrastructure.CustomerDto[] customers = ReadCustomersFromTheDatabase();...

> So it's basically having a separate persistence layer? Pretty much. It's all in the 'infrastructure' layer (in the Onion/Clean Architecture world). Similar to your code; the mapping is either...

Looking to close a few issues. With the changes made to Vogen and the updated documentation, is there anything missing in the documentation, or can this be closed?

Is that necessarily a problem with generated code? Does it reference _your_ `Infrastructure` layer or merely references dapper/ef assemblies? I can understand the problem if it was hand-crafted code, as...