Hello -

Quick question for you. I have a set of services which use LLBLGEN at the DAL layer. Many of the services are distinct and not related to the other. Although they share the same identity to log in between services.

Here's my "good pratice" question. Should I build a number of LLBLGEN projects looking at different tables in the database, or is it a good idea to use a single selfservice which represents the entire table collection in the database?

I'm expecting to have between 20 - 50 tables when the project is complete.

I am worried about performance in terms of lumping them all into one LLBLGEN project, but conversely worried about integrity if they only look at the tables peice meal.

Phil.

For proper division between the various services, I think it's wise to create a project per service (or one project and just select the entities you want to include for the generated code for that service). Though only for division between the services. You can also opt for a single project and use it in every service, though then you can 'cheat' by using entities originally meant for other services in a particular service.