Hi,

I did a quick search and on how to handle using LLBLGen and source control. I was surprised at the number of people that keep the generated code in the repository rather than the LLBLGen project itself except it does make it a pain to compare changes. (Normally I have to checkout the older project and do a catalog refresh to see the changes).

Since migrating to the new 1.0.2004.2 version I have noticed that there is a nice log output of changes when doing a catalog refresh and I thought of possibly saving this into source control to keep a history of changes but this isn't as helpful when wanting to do a text comparison using a diff.

I then wondered how the LLBLGen project file format currently works and if it would be possible to serialize it to a more diff friendly XML format when LLBLGen is used in conjuction with a source control system.

Comments?

Tim

It was XML when I started, but the amount of information in the project file is huge, as the catalog information is there too. It soon became very slow in larger projects so I moved to binary serialization.

You can save the refresh log in XML format, which you can use further for processing in your own systems if you'd like.