This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I was reading up on dist apps in the help file and came across this: "LightSpeed entities should not be exposed directly at service interfaces. Instead, we recommend that services expose data transfer objects—simple, dumb, “plain old data” objects that carry the required property data. Use helper methods to copy data between entities and the corresponding DTOs." You guys probably realise I'm going the Mono route and like many other dev's I needed 'plain old data' objects to glue stuff together. So I read Ivans article, Customising LightSpeed entity templates: http://www.mindscape.co.nz/blog/index.php/2009/09/16/customising-lightspeed-entity-templates/ With 2 simple changes I can generate en entire DTO project, attached, how cool is that! |
|
|
|
|
Ok I needed a slight adjustment to the Fields.vm file. To get the DTO project to compile tho I need to remove the "ModelUnitOfWork" partial class, how do I do that? Cheers,
|
|
|
|
|
The ModelUnitOfWork class is declared in DataContext.vm. If you remove that #parse from Base.vm, then ModelUnitOfWork will not be generated. |
|
|
|
