FAQ/Izenda-Update-Best-Practices.md
... ...
@@ -1,25 +1,21 @@
1
-##When you update Izenda, you should perform a few steps:
1
+##Updating within a point release - a 'Maintenance Update' - (Ex: 6.9.0.1-> 6.9.0.3)
2 2
3
-###If you are upgrading within a point release - a 'Maintenance Update' - (Ex: 6.8.0.1-> 6.8.0.3)
3
+1) Set aside any customized files in /Resources - This is typically CSS, but could be HTML or JS.
4 4
5
-1) Preserve any customized files in /Resources - This is typically CSS, but could be HTML or JS.
5
+2) Copy the /Resources & /BIN from the Izenda 'Maintenance' download and replace the existing folders
6 6
7
-2) Remove /Resources & /BIN completely.
7
+3) Compare customized files from Step #1 to new updated files and copy your customizations to new files one at a time, testing each.
8 8
9
-3) Replace with updated /Resources & /BIN from the Izenda 'Maintenance' download.
10 9
11
-4) Compare customized files from Step #1 to new updated files and merge over your customizations to new files one at a time, testing each.
10
+##Updating across point releases (Ex: 6.8.0.1-> 6.9.0.3)
12 11
13
-
14
-###If you are upgrading across point releases (Ex: 6.7.255-> 6.8.0.5)
15
-
16
-1) Preserve any customized files in the entire Izenda deployment - This is typically the global.asax, code-behind files, sometimes individual page code, CSS, HTML or JS.
12
+1) Set aside any customized files in the entire Izenda deployment - This is typically the global.asax, code-behind files, sometimes individual page code, CSS, HTML or JS.
17 13
18 14
2) Download an Izenda 'Full Download' that includes all files and pages.
19 15
20
-3) Launch this 'vanilla' installation with only license key. You should be sent to the settings.aspx page to ask for a connection string.
16
+3) In the 'vanilla' kit, enter the connection string and license key into the Global.asax. Launch the 'vanilla' installation to confirm that your license key and connection string are set correctly.
21 17
22 18
4) Compare customized files from Step #1 to new updated files and merge over your customizations to the new files, starting with the global.asax and connection info (if contained somewhere besides the global). Move over customizations one at a time, testing each.
23 19
24 20
_See Also:_
25
-[[How-do-I-upgrade-my-6-7-RI-with-a-6-8-DLL]]
21
+[[How-do-I-upgrade-my-6-7-RI-with-a-6-8-DLL]]
... ...
\ No newline at end of file