Migration to newer version of LLBLGen

Posts   
 
    
PatLac
User
Posts: 2
Joined: 27-Aug-2007
# Posted on: 27-Aug-2007 17:28:55   

Hi,

I am currently working for a client who used LLBLGen Pro to develop an application.

The development for this application was started around the end of 2005 and used VS 2003 and LLBLGen version 1.0.2004.2 Final (Released On July 13 th 2005).

We are wondering how (if possible ) we can upgrade the application to the latest version of Visual Studio and also the latest version of LLBLGen Pro.

Is there a "migration path" for LLBLGen ?

Do you know of other clients who needed to do a similar migration?

Thanks a lot for your input !

Patrice

goose avatar
goose
User
Posts: 392
Joined: 06-Aug-2007
# Posted on: 27-Aug-2007 18:19:09   

Hi Patrice, if you want to upgrade to llblgen2.5 there is a section in the documentation that can be useful (Migrating your code).

I've migrated my code from llblgen 1.0.2005.1 Final (March 31st, 2006) to the latest 2.5 and almost everything went smoothly, and for the few issues that come up there was always a easy workaround.

Please try these steps and let me know if something goes wrong:

1. First of all check throughly for custom user code regions and other kinds of custom user code a make a backup.

2. Open your llblgen project file (.lgp) in the new llbl designer(2.5)

3. Refresh the catalog in case something has changed since the last time the project was open. (remember to check newly added entities)

4. Press F7 to bring the generation process dialog

5. Male sure that everything in the Generation Settings tab is correct (target language, template group, root namespace and Target platform)

6. In the Template Bindings tab make sure that the SD.TemplateBindings.SharedTemplates.BackwardsCompatibily.Net20 is the first listed template.

7. In the Task queue to execute look for the SD.Tasks.Generic.PredicateFactoryClassGenerator and the SD.Tasks.Generic.SortClauseFactoreClassGenerator and check the IsEnabled checkbox.

8. Save the preset as you prefer for future occasions.

9. Start the generator

10. replace the newly generated code with the one in your protect

11. rewire the references

12. start the replacing and refactoring of the custom user code that you backup ed in the step 1.

at this point almost everything should work fine but since I don't know the specific details of the custom user code (if any) in your project is probable that some bugs would araise.

Good luck!

Goose.

PatLac
User
Posts: 2
Joined: 27-Aug-2007
# Posted on: 28-Aug-2007 14:52:15   

Thanks very much for this info !

We will try that in the near future and I will tell you all how it went !

Thanks again for the quick answer !

Patrice