Comments on: DTOs, Data Contacts and code generation http://www.mindscapehq.com/blog/index.php/2009/01/28/dtos-data-contacts-and-code-generation/ The official blog of Mindscape Sun, 13 May 2012 21:07:01 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: CSA http://www.mindscapehq.com/blog/index.php/2009/01/28/dtos-data-contacts-and-code-generation/comment-page-1/#comment-28919 CSA Tue, 03 Feb 2009 17:52:44 +0000 http://www.mindscape.co.nz/blog/?p=457#comment-28919 Brilliant! Brilliant!

]]> By: Ivan Towlson http://www.mindscapehq.com/blog/index.php/2009/01/28/dtos-data-contacts-and-code-generation/comment-page-1/#comment-28831 Ivan Towlson Mon, 02 Feb 2009 01:06:22 +0000 http://www.mindscape.co.nz/blog/?p=457#comment-28831 Hi Donovan, Just to let you know that the inheritance issue will be addressed in LightSpeed 2.2, which should be out very soon. Hi Donovan,

Just to let you know that the inheritance issue will be addressed in LightSpeed 2.2, which should be out very soon.

]]> By: John-Daniel Trask http://www.mindscapehq.com/blog/index.php/2009/01/28/dtos-data-contacts-and-code-generation/comment-page-1/#comment-28784 John-Daniel Trask Fri, 30 Jan 2009 21:52:25 +0000 http://www.mindscape.co.nz/blog/?p=457#comment-28784 Hi Donovan, Thanks for your feedback! We will be making significant enhancements to LightSpeed's code generation and distributed features (DTOs, WCF support etc) in LightSpeed 3.0 which we begin development on next week. This feedback will likely directly result in enhancements that you're asked for here. This features was added fairly quickly to address a request that an existing customer had and we thought it was a good start. It is just that though - a start :-) The templates use NVelocity for the templating engine - there is documentation floating around regarding this online. We'll be improving our guidance around working with the templates in the future as we continue to move down the code-generation road. Do feel free to hack around with them but do back them up so you don't accidentally revert them when you install a newer version of LightSpeed. Hi Donovan,

Thanks for your feedback! We will be making significant enhancements to LightSpeed’s code generation and distributed features (DTOs, WCF support etc) in LightSpeed 3.0 which we begin development on next week. This feedback will likely directly result in enhancements that you’re asked for here.

This features was added fairly quickly to address a request that an existing customer had and we thought it was a good start. It is just that though – a start :-)

The templates use NVelocity for the templating engine – there is documentation floating around regarding this online. We’ll be improving our guidance around working with the templates in the future as we continue to move down the code-generation road. Do feel free to hack around with them but do back them up so you don’t accidentally revert them when you install a newer version of LightSpeed.

]]> By: Donovan Hide http://www.mindscapehq.com/blog/index.php/2009/01/28/dtos-data-contacts-and-code-generation/comment-page-1/#comment-28780 Donovan Hide Fri, 30 Jan 2009 17:11:33 +0000 http://www.mindscape.co.nz/blog/?p=457#comment-28780 Tested it out a little bit! Would be good if inherited properties from the base type were also include in the code generation. Eg. Event.HelpText is include in the AskingPriceEvent DTO. Another idea would be flattening out related entities' properties to a certain specified depth. This could get complicated but would be very useful. Some inspiration from here maybe? http://structuremap.sourceforge.net/Generics.htm Tried manually editing the DataContracts.vm, but don't want to reverse engineer your templating language! Is it NHaml-derived by any chance? Tested it out a little bit! Would be good if inherited properties from the base type were also include in the code generation. Eg. Event.HelpText is include in the AskingPriceEvent DTO.

Another idea would be flattening out related entities’ properties to a certain specified depth. This could get complicated but would be very useful. Some inspiration from here maybe?

http://structuremap.sourceforge.net/Generics.htm

Tried manually editing the DataContracts.vm, but don’t want to reverse engineer your templating language! Is it NHaml-derived by any chance?

]]> By: Donovan Hide http://www.mindscapehq.com/blog/index.php/2009/01/28/dtos-data-contacts-and-code-generation/comment-page-1/#comment-28774 Donovan Hide Fri, 30 Jan 2009 14:59:57 +0000 http://www.mindscape.co.nz/blog/?p=457#comment-28774 Hi, this will be a good timesaver and give finer grained control by including rather than excluding properties essential for serialization, which XmlIgnore (and ScriptIgnore) sufferred from a lack of. Will it be possible to include generated fields like LockVersion and ID, which would be essential in allowing serialized entities to be updated remotely and then reattached to a Unit Of Work? Would be nice to see a working sample where JSON is used as the transmission format, perhaps even using JSON.NET rather than WCF. Cheers, Donovan. Hi,
this will be a good timesaver and give finer grained control by including rather than excluding properties essential for serialization, which XmlIgnore (and ScriptIgnore) sufferred from a lack of. Will it be possible to include generated fields like LockVersion and ID, which would be essential in allowing serialized entities to be updated remotely and then reattached to a Unit Of Work? Would be nice to see a working sample where JSON is used as the transmission format, perhaps even using JSON.NET rather than WCF.
Cheers,
Donovan.

]]>