Two questions please:

Q1) I have version 2.6 already installed on my machine. When I install version 3.0, is it a side by side install or upgrade 2.6 to 3.0?

Q2) Projects created in version 2.6 can be opened in version 3.0 and say some changes made, save the changes. Is it now possible to open the project in version 2.6. Is it possible to open the same project file in version 2.6 and 3.0 without any conversion to the project file?

At present I am using LLBLGen Pro version 2.6.

A1) Side by side deployment.

A2) Once the project file is migrated to v.30 it won't be opened in v.26. So you should keep a backup copy of the v2.6 version in case you needed to fall back.

Small correction on 2: a lpg file is 'exported' to a v3 llblgenproj file which is xml. So your lpg file is unaffected in this process. You can't open a .lgp file in v3, you have to convert it in v2 to v3's project format by running a conversion template.

Q3) will my code continue to work with no changes after upgrading from v2.6 to v3.0 and compiling the new solution?

morten71 wrote:

Q3) will my code continue to work with no changes after upgrading from v2.6 to v3.0 and compiling the new solution?

You have to migrate your own code, see the v3 'migrating your code' for the breaking changes. This might require some changes (minor mostly) to your own code, which won't work with v2.6 code, so make a backup of v2.6's version so you can go back.

Where can I get this 2.6 to 3 project file upgrade template?

Thanks

In v.3.0 downlaods.

Hi Walaa,

Doesn't this mean I have to upgrade before I can trial the upgrade of my 26 project?

Thanks Matt

I am going to upgrade now anyway as LLBLGen has proven invaluable in past, but might we worth thinking about.

bentos wrote:

Hi Walaa,

Doesn't this mean I have to upgrade before I can trial the upgrade of my 26 project?

Thanks Matt

It's also available on the demo trial page: http://www.llblgen.com/pages/demo.aspx

At the bottom. Perhaps you didn't scroll to the bottom. We'll add a note at the top for when a user doesn't scroll all the way down.

Thanks Otis, yep, missed that scroll! have upgraded now and am in the midst of a .net 4 upgrade, I will shout any issues!

Otis wrote:

morten71 wrote:

Q3) will my code continue to work with no changes after upgrading from v2.6 to v3.0 and compiling the new solution?

You have to migrate your own code, see the v3 'migrating your code' for the breaking changes. This might require some changes (minor mostly) to your own code, which won't work with v2.6 code, so make a backup of v2.6's version so you can go back.

Otis, where can I find this "migrating your code" info?

Migrating your code