Skip to main content

Upgrading to a newer version

Q: Are there backward compatibility issues when we upgrade from an older version of Blaise 5?

Normally no, but between 5.0.5 and 5.2 security tokens were added to the system, so anything from before 5.2 is not compatible with 5.2 and higher. Re-preparing will solve this.

Q: What happens to my Resource Database when I upgrade to a newer version?

New functionality will be incorporated into your .blrd, but we won’t touch any templates. Note that on rare occasions, it is possible that our implementation of some properties has changed and this might affect your templates as well.
To make use of new default templates, copy/paste them from the default Resource Database into yours or adjust your settings to match the new templates.

Q: What is the minimum required Blaise/DepApp version for my CMA version?

CMA Version

 

Minimal Blaise

runtime / DepApp version

 

2.606

5.12 >

2.6

5.11 >

2.5

5.11 >

2.07

5.10.13 >

2.06

5.10 >

2.0

5.10 >

1.5

5.9.6 >

1.05

5.8.3 >

1.0.3

5.8.2 >

 
 
 

CMA Admin tool

 

Minimal Blaise

runtime / DepApp version

 

1.5

5.12 >

1.0

5.10 >

Q: What kind of issues might occur if we upgrade to a newer version of Blaise from an older Blaise 5 version?

Your layout may be affected, so you may need to fix that. The Blaise Team tries their best to keep any effects as small as possible of course.
5.0.5 and 5.2 (or higher) are not compatible because of added security tokens. So recompiling will be necessary if you upgrade from 5.0.5 or lower to 5.2 or higher.

Gaining deeper understanding