locked
SharePoint 2010 team development approach RRS feed

  • Question

  • I need suggestion on SharePoint Team Development Approach Selection. 
    
    Goal of Our SharePoint Developments:  
    .         Our working component should keep in file system as much as
    possible. Because we need to manage our files through source control
    repository.Our development should be follow n tier architecture.
    
    .         Easily work with a team with parallel development.
    .         Easily deployable and testable. 
    
    So far I found 2 development approaches to achieve that goals. These
    approaches are: 
    
    1.       WebPart/Visual WebPart Base Development.
    2.       Custom Aspx Page(Application Page) Development. 
    
    WebPart/Visual WebPart Base Development: 
          How To:
    .         Need to decompose our user interface level functionality into
    WebParts.
    .         This webparts are deployed to the server.  
    .         Create Wiki/Webpart page for hosting that webparts for visible
    from browser.
     Advantages:
    .         Our user interface related rendering logic are decomposed. So
    easily.
    
    It provide more flexibility to manage, change, enhance, identify and fix
    bugs more easily.
    .         Easily reusable from different wiki/webparts pages. 
    
    Disadvantages:
    
    .         When deploying our web parts to another machine then our local
    server Pages cannot be deployed. Because those pages are stored at
    SharePoint database note in our codebase(file system).
    Need database backup-restore. But it may override others work. 
    
    Custom aspx Page base Developemnt:  
    
    How To:
    
    .         We decompose our User interface level functionality into ASP.Net
    WebForm.(Sharepoint Application Page)
    
    Advantages:
    
    .         Our complete code base is in our file system. 
    .         We can easily work as a team with our pages.
    .         We are very familiar with this approach. Because we develop
    current asp.net project like that way. 
    Disadvantages:
    .         Always need tricky solution.
    .         Do not reuse rendering logic though code is in web page.  
    
    If any suggestion or better approach other then that are welcome!!!.
     
    Thanks 
    

    Ahasan Habib [Only 3 things can reach you to success. 1. Industry 2. Industry 3. Industry]
    Saturday, October 22, 2011 6:31 AM

Answers

  • The first approach is better because custom application pages are globally deployed and that may not be the desired use for them. However, instead of webparts, I'd recommend writing user controls thus simplifying your deployment procedures for each component.

    Pranav Sharma
    SharePoint Consultant, Portal Solutions
    • Proposed as answer by Shimin Huang Monday, October 24, 2011 2:12 AM
    • Marked as answer by Shimin Huang Friday, October 28, 2011 6:40 AM
    Saturday, October 22, 2011 11:52 PM