☰

Updated Izenda Update Best Practices (markdown)

CaseyStokes committed 2015-08-05 11:40:51 -0400 commit d154a38ca132b67ac751c0c01fe959e1b199c207

				FAQ/Izenda-Update-Best-Practices.md
			
          @@ -7,7 +7,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.

          -##Updating across point releases (Ex: 6.8.0.1-> 6.9.0.3)

          +##Upgrading across point releases (Ex: 6.8.0.1-> 6.9.0.3)

           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.

...	...	@@ -7,7 +7,7 @@
7	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	9
10		-##Updating across point releases (Ex: 6.8.0.1-> 6.9.0.3)
	10	+##Upgrading across point releases (Ex: 6.8.0.1-> 6.9.0.3)
11	11
12	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.
13	13