Versions
Joined: 24-Dec-2009
pt wrote:
Can someone briefly explain how the LLBL versioning works? The latest build of 2.6 on the website shows a release date of 24-Dec-2009 and build date of August 26th. If I install it and run the main executable, the Help > About says release date is October 9th, 2009.
Then we made a typo in the item on the website. Will correct that
So there are 3 dates in total and none of them match. So what does each date represent and how could I best tell what version I have so I can correlate it to the website to know if I'm running the latest? Thanks
The system has various parts and they're not versioned together, as updating a runtime lib to a newer build doesn't require you update the designer.
The following parts are each versioned as a separate unit: - the designer and its core assemblies - the task performers (code generator assemblies) - the runtime libraries - the templates - the drivers
This means that if the designer is updated because its core assemblies got an update, the runtime libraries aren't getting a new version and vice versa.
The about box shows the build date of the designer assemblies. So if the website (after we've corrected that typo 
) shows the about box should display October 12th, and your version does, you have the latest designer build.
The runtime libraries are a different unit (that's also why you can download them separately), and have different versioning. This is also because runtime libraries change more than the designer.
I hope this is a bit more clear. I know it can be a bit confusing in the beginning, but if you look at the various parts, it's easier this way, as you can update the parts manually without the necessity of uninstalling and re-installing the whole system.
The full installer always has the latest builds of everything. Every item in the download section shows the build date (mmddyyyy) of the element.
Thanks for the heads up on the build date, I'll correct that.