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
|
My project is an ASP.NET MVC application. Its data model has about 200 tables. The tables can be logically divided into modules. For example, user management module, UI configuration module, and business entity module, etc. Some modules are almost identical across different projects. What is the best practice, in the context of LightSpeed ORM, to modularize the data model, and reuse some modules in other projects? |
|
|
|
|
Is the model interconnected? (e.g. all 200 tables are connected either directly via relationships or implicitly due to function) - generally you should have your model seperated out into its own assembly if you are going to be re-using it across components in your solution. Can you elaborate a bit more on what you are looking to achieve in terms of re-use?
|
|
|
|
