FAQ/Izenda-Update-Best-Practices.md
... ...
@@ -1,14 +1,18 @@
1 1
##Updating within a point release / Performing a 'Maintenance Update' (Ex: 6.9.0.1-> 6.9.0.3)
2 2
3
-1) Set aside any customized files in /Resources - This is typically CSS, but could be HTML or JS.
3
+1) Review release notes [here](http://wiki.izenda.us/Release-Notes). Release notes for each maintenance release will have notes detailing changes, settings, and fixes associated.
4 4
5
-2) Copy the /Resources & /BIN from the Izenda 'Maintenance' download and after removing your old /Resources &/BIN directories completely, replace with the new folders.
5
+2) Set aside any customized files in /Resources - This is typically CSS, but could be HTML or JS.
6 6
7
-3) Compare the customized files from Step #1 to new updated files and copy your customizations to new files one at a time, testing each.
7
+3) Copy the /Resources & /BIN from the Izenda 'Maintenance' download and after removing your old /Resources &/BIN directories completely, replace with the new folders.
8
+
9
+4) Compare the customized files from Step #1 to new updated files and copy your customizations to new files one at a time, testing each.
8 10
9 11
10 12
##Upgrading across point releases (Ex: 6.8.0.1-> 6.9.0.3)
11 13
14
+1) Review release notes [here](http://wiki.izenda.us/Release-Notes). Release notes for each release will have notes detailing features, settings, and fixes associated.
15
+
12 16
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.
13 17
14 18
2) Download an Izenda 'Full Download' that includes all files and pages.