Hi,

How does LLBLGen Pro handle difference versions in a project?

Is it possible at all?

Kind Regards,

adb.

different versions of what?

Sorry, I can't come up with one word descriping all this, so I hope I can explain it insteed.

After 1 year in my compagny I will release Version1 right.. After Another year, I release Version 2 with new features and stuff.. and so on. So lets say I have relased 3 versions, how can I keep track of all my changes, is there somekind og tags on each changes? Or even better, some kind of merge tool for this?

Specific example: A change could be if I wanted to rename a colum name, from one version too another.

In V3 you'll be able to load a .lgp file and save the dsl text files and vice versa, so this should be sufficient to put the project in a third-party version control tool (http://llblgen.com/TinyForum/Messages.aspx?ThreadID=13165)

Thx, but I can't wait for '09 Q1.

The other option is to put the generated code under version control, so you can track changes in the generated code.

Everytime you refresh the catalog LLBLGen Pro optionally archives the older *lgp file (it renames it appending a dateTime string), this also can be saved in the Source Control system, so you can revert back to it whenever you want.

To link the generated code with the *.lgo file, before generating the new code, you may label the existing generated code (in source control)with the same name of the archived lgp file.