During development of the 8.2 release, the development team has made architectural change in order to support some of the 8.2 code and process changes:
1. The removal of client specific configurations to isolate them to client specific configurations files.
2. The introduction and move toward new technologies that include MVC and NHibernate.
3. Solidifying the application into one buildable solution with a compiled web source.
The impacts of these changes include:
1. A new patch creation process that will create a patch specific to each client and their individual configuration and deployment.
2. The need for a new database role to support update and insert to the database for use by MVC.
3. The removal of connection strings and client specific keys from the web.config. These will now be found in files in the web/config folder.
4. The removal of virtual directories from the web for web services, (it is important that deployment instructions are followed to remove these in order for web services to work correctly).
5. The exclusion of code behind files for the web source. (there will no longer be aspx.cs files included in the deployment as they will be compiled into a library).
Outside of the new 8.2 functionality, the areas that were identified as being high impact based on architecture changes were:
· Account Creation
· Client Web Services
· Web Parts
· Calendar/Booked Resources
· Ratings & Reviews
· Upload Attachment to Grades Administration
Client should pay special attention to these areas during the UAT period of the 8.2 Release.