Koen vosters improving-yoursp_solutiondesign-spsbe13
by BIWUG on May 04, 2012
- 351 views
SharePoint 2010 can be a complex beast. As a developer there is an extensive API that you have to master, lots of xml, code, files and configurations. ...
SharePoint 2010 can be a complex beast. As a developer there is an extensive API that you have to master, lots of xml, code, files and configurations.
All of that needs to be deployed to your SharePoint farm in a proper way.
In the worst case scenario your deployment will be done by someone who hasn’t a clue about SharePoint development and would rather not have your solution on their farm as it will increase the risk of downtime. This session is about designing SharePoint solutions that will enable future solutions to be built besides or on top of it. Even if there are guidelines on the best practices to write SharePoint code, this specific topic will not be our main focus during the session.
It will give you a real life example of how combination of several projects done by multiple parties can be successfully deployed simultaneously. As a result of this approach we were able to build different public internet sites and put them into production at the exact same moment.
This session aims to create awareness that you, as a developer, are required to build a solution which will be deployed on a shared environment. Showing how these projects were designed and managed and what lessons we learned during the process will help you to reduce the risks of the deployments.
- Total Views
- Views on SlideShare
- Embed Views