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
|
Hi, When you split large models into smaller sub-sets, LightSpeed still expects all links to the 'actual entity' to be present in the model that has the 'actual entity'. For example: Model1 has these two entities:
Model2 has these two entities:
Model3 has these two entities:
When you now press "Check links" it will give a warning that there's no link between User and Role in file Model2 and no link between User and Audit in file Model3. To get LightSpeed to work 'correctly' you need to add a link to Role and Audit in Model1. This makes split models tedious to work with and almost force you to add a new model containing the 'actual' user entity with all it's links. Can this requirement be removed? It would make split-models a lot more attractive. Regards, Jerremy |
|
|
|
|
Thanks for the suggestion - Ive added this to our backlog for future enhancements. We would love to hear from anyone else who would be interested in this! In the meantime I give you an update once I have had a look to see whats involved with this and if its possible to get something into the nightlies.
|
|
|
|
|
Extra feedback: This is what stopped me from using split models. |
|
|
|
|
Same here. |
|
|
|
|
Thanks for the feedback - interesting to hear it impacted a good number of you. One of the challenges is that even with how it works now required an absurd amount of hacking around the DSL tools built into Visual Studio to make it happen. It's not ideal because of the hoops we had to jump through. I recall years ago hearing that improvements would be coming to improve support in the DSL tools itself so it's probably a good time to investigate if it's improved in Visual Studio 2012. Thanks! John-Daniel |
|
|
|
