Fork me on GitHub
The journal that this archive was targeting has been deleted. Please update your configuration.
« The Juicy Pattern | Main | Why another framework? »

Why for SharePoint?

For SharePoint Developers, it’s really an easy answer: SharePoint extends ASP.NET WebForms, so anything that facilitates the development of a SharePoint Farm Application would be useful. In fact, SharePoint 13 still uses ASP.NET WebForms, the same way SharePoint continues to use COM objects (yes, there are still alive).

Learning a new programming language or a new framework is not the challenging part of being a SharePoint Developer, the most difficult part, at least for me, is dealing with poorly written applications with no software standards or conventions and trying to work with other developers as a whole team and at the same time maintaining a clean application. So, the goal of Juicy Presentation Pattern is to introduce an MVC like pattern to have Separation of Concerns (SoC), introduce Convention-over-Configuration (CoC) for consistent and maintainable application and emphasize modularization for easier Test-Driven Development  (TDD) for ASP.NET WebForms.

References (57)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>