Customizeable LightSpeed-Model

Hi,

is it possible to customize an exisiting LightSpeed model in another vs-project (plugin project to our app)?
If not, wouldn't it be a nice key feature for LightSpeed 4? :D

My Test-Project:



My Main-Model:



My Custom-Model:



My Workflow:

1. Create a project with LightSpeed model (Main)
2. Add some entities to main model and save the model
3. Create a project with LightSpeed model (Custom)
4. Set custom model as linked child
5. Add an entity from main model and set as link
6. Add some entities to custom model
7. Assign entity to linked entity
8. Create inheritance from entity to linked entity
9. Save custom model - error message:
   
   'External reference Address specifies an inheritance relationship.  Inheritance may not be defined on links.'
10. Compile - error message:
    
    'The type or namespace name "EntityName, in my case Address" could not be found. (Are you missing a using directive or an assembly reference?)'
11. Add main project assembly reference to custom project
12. Add using directive to generated code from custom model
13. Compile - successfully, but the uow of custom model does not contain the entities of the main model and the LightSpeed-Designer throws error (see point 9)

I don't think that it's so difficult to change LightSeed to ensure that an existing model would be customizable.
The entities of the main model must not be rename- or erasable, but in a custom model i want to add
new associations (incl. inheritance) to linked main-model-entites and create new fields/properties as well.

So you had a new group of customers, the customers of your customers. :D
Whenever one of our customers want to customize our product, they would need your LightSpeed.

I hope my English was not too bad, and you understand what I want. ;)


Best regards from Hannover in Germany,
Chriss

Linked models work through partial classes, which means all linked models must be in the same project (if that weren't enough, all associations are bidirectional, which means you can't split an association across projects because each would have a dependency on the other).  So we don't really support 'plug-in'-type composition of models at the moment.

That said, we are talking to another potential customer who also wants 'plug-in-able' models, so we will keep looking at this to see whether we can improve our support for it.  Thanks for the suggestions and feedback!

I would be very glad to get feedback when there is something new.
That would be one of our main reasons for the use of LightSpeed .

Best regards,
Chriss