Upgrade and Maintain Customizations
This documentation is for the legacy Izenda 6 product. Documentation for the new Izenda 7 product can be found at https://www.izenda.com/docs/
About
Izenda requires two repositories to be forked; Resources and Reference-Implementations. The resources repository is where the HTML, CSS, and Javascript reside within the Izenda application. The Reference-Implementations repository is where the various RI kits for Izenda are stored. As of now, this includes the Webforms-CS, Webfomrs-Vb, MVC4R2 and MVC5R3 kits. These repositories are public to allow customers to be able to modify the resources on an as-needed basis. In order to keep up with changes we make to these repositories, it is prudent to fork them to keep up with all the updates while maintaining any customizations you might create on your own.
How to fork
To fork the repositories, you will need a github account. This can be obtained through your organization or personally and is a straightforward process. Once you have a github account, visit our resources repository page and our reference implementations repository page. There will be a button at the top of the page that says "Fork". Click this and the repository will be added to your personal repositories.
You can now make edits to the resources and kits in your repositories without worrying whether you're going to break functionality. Now whenever you update your Izenda.AdHoc.dll to the latest version, instead of copying the Resources or RI from the zipped archive, you will go to your github interface tool (usually a command line, but GUIs are available) and fetch the upstream repository. If there are any conflicts when fetching, you can resolve these using a merge tool. Ideally, there will be no conflicts and your resources will be updated with both your changes and any changes made by us in development. This will allow you to stay current and prevent you from losing any of your own work.