FAQ/Izenda-Update-Best-Practices.md
... ...
@@ -0,0 +1,22 @@
1
+##When you update Izenda, you should perform a few steps:
2
+
3
+###If you are upgrading within a point release using a 'Maintenance Package'(Ex: 6.8.0.1-> 6.8.0.3)
4
+
5
+1) Preserve any customized files in /Resources - This is typically CSS, but could be HTML or JS.
6
+
7
+2) Remove /Resources & /BIN completely.
8
+
9
+3) Replace with updated /Resources & /BIN from the Izenda 'Maintenance' download.
10
+
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.
12
+
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.
17
+
18
+2) Download an Izenda 'Full Download' that includes all files and pages.
19
+
20
+3) Launch this 'vanilla' installation with only license key. Should be sent to settings page to ask for a connection string.
21
+
22
+4) Compare customized files from Step #1 to new updated files and merge over your customizations to 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.
... ...
\ No newline at end of file