Hello,

This is just an open ended question to ask how people are handling the sharing of multiple .lgp file changes in an environment where the entities are shared across teams?

For example, we may have Team A working on change set A, required a certain set of entities, generated through their version of the source controlled .lgp designer project file, while at the same time another team B is working on change set B, with their version of the .lgp designer project file.

We use a checkout-development-merge scenario with our use of source control. so the .lgp files are not 'LOCKED' when checked out. Is there any way to 'MERGE' the .lgp files (a utility?) since they appear to be binary, or must team A and B co-ordinate .lgp designer project updates and ensure all changes are made to 1 copy of the .lgp file and of course a combined set of entities generated?

Thanks.

Can1

This has been addressed some times. Please read this: http://llblgen.com/TinyForum/Messages.aspx?ThreadID=10707 http://llblgen.com/TinyForum/Messages.aspx?ThreadID=13165

Unfortunately, indeed, you can't merge them. In v3, things are stored in XML, so this problems will go away. We did try to write a merger tool, but it appeared to be too difficult, as we lacked history info on the data (change tracking wasn't build in so we couldn't correctly merge things properly)