Each team members of my team is responsible to develop a moudle of a system, all of them may change database structure according to their needs.
We are using vss to control version, they would create a new branch before they start to create new function, and they merge all modified files to main branch when they complete it. Therefore, they can develop their function independently in their branch and the main branch would keep all of their works.
However, llblgen project file is a binary file, it cannot be merge. The ways we do now is that check out llblgen project and entity classes in main branch and modify it, then create a sql script for database changes before check in, and send it to each members to update their database in order to prevent losing entities or fields next times they refresh the catelogs.
The main problem is that we need to build a release periodically, but some member may not finish their complex function, the release would not include files for those functions. But database and entities changes made by those members are checked in already, so I open llblgen project and rollback changes made by those members and generate files again before I build release.
I believe if llblgen project file is xml based, it would solve the problem easily, like the csproject file in vs.net, they can merge it to main branch when they check in, therefore it will not affect other members if they change database structure in their own branch, everyone can work independently and happily.
All members sharing the same llblgen project, all members are inter-dependent now, it is inefficient when developing a system in a team. Do you have any suggestions on handling this suitation?