How compatible are the new template sets compared to the old sets? We have applications that use the old template sets. Should we keep on using the old template sets if we were to regenerate the llblgen code for them or can we use the new template sets and not break existing code? If we choose to use the old template sets, is it possible to run the old sets and the new sets side-by-side?

Any advise on this would be helpful.

TlighT wrote:

How compatible are the new template sets compared to the old sets? We have applications that use the old template sets. Should we keep on using the old template sets if we were to regenerate the llblgen code for them or can we use the new template sets and not break existing code? If we choose to use the old template sets, is it possible to run the old sets and the new sets side-by-side? Any advise on this would be helpful.

The issues for migrating code are in the section 'migrating your code' in the documentation (grab the latest from the website ). THe issues are minor, only some 1:1 relations will be named differently, if you re-generate the code using the new templates and you use the old BL/GUI code you wrote against the older generated code. These can be fixed easily and you're upgraded.

Upgrading existing applications to the new runtimes/templates is recommended if these applications will get additional functionality later on. We keep versions of 1.0.2003.2/3 and their templates in our sourcecontrol databases so if you want you can always go back.

Running them side by side is possible, if you sign your generated code assembly as well. When you do that, you can specify which version to use in the .config file of your application: either use 1.0.2004.1 based version or the older one. However you also have to re-compile your own code against the new 1.0.2004.1 runtime library.