Last updated on January 12, 2014
The largest SharePoint application that I’ve designed so far, which I have yet to blog on architecture, began with the desire to roll a no code solution.
12 months later from the time that it hit the meeting rooms and white boards my team has accomplished a great deal. Some of it was bending the platform to do the complex things our business folks required. During a scheduled refactor we are finding opportunities to dramatically improve performance … and leaving behind certain no code paradigm structures.
We ended up with a full blown, well documented SharePoint 2010 solution after all. Several Visual Studio sequential workflows, an event receiver, a couple application pages, a robust InfoPath template leveraging the declarative rules engine along with a fully featured VSTO code behind. All this supporting a large number of transactions, which in the end, puts money in peoples pockets.
There is always a time and a place for various strategies. As our application supported larger and larger numbers of people, refactoring out the no code paradigm aspects has definitely proved worth the effort. Both to improve performance and scale to larger use thresholds.