SharePoint Application Development
Download
1 / 7

SharePoint Application Development Best Practices with Rapid Tools - PowerPoint PPT Presentation


  • 84 Views
  • Uploaded on

SharePoint Application Development Best Practices with Rapid Tools. http://rapid-tools.googlecode.com. Clint Simon [email protected] Custom Application Development Best Practices. What‘s the problem?. SharePoint development guidance for custom application development is flawed

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' SharePoint Application Development Best Practices with Rapid Tools' - yuri


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

SharePoint Application Development Best Practices with Rapid Tools

http://rapid-tools.googlecode.com

Clint Simon

[email protected]



What s the problem
What‘s the problem?

  • SharePoint development guidance for custom application development is flawed

    • “Naturalists” and Application Developers use parallel development processes on a shared environment

    • SharePoint is used for version control of assets stored in the content database

    • Traditional source control is used for all assets stored on the files system and source code

    • Read more: http://msdn2.microsoft.com/en-us/library/bb428899.aspx

  • Why doesn’t this work?

    • There is a hard dependency between content database assets and compiled assets

    • It is very difficult to keep all the assets in sync

    • Automated processes are nearly impossible

    • Deploying a clean build to a new environment is very painful

    • Software Development Life Cycle (SDLC) is not supported


Sharepoint missing pieces
SharePoint Missing Pieces

Key Blocking Issue: Visual Studio SharePoint extensions is not a complete IDE solution.

Key Blocking Issue: There is no robust provisioning framework for SharePoint.


A solution
A Solution

  • IDE Tools – Rapid Tools SPDeploy

    • Create all customization inside visual studio

    • Compile and deploy a wsp remotely

  • Single Source Control repository

    • Because all SharePoint customization are now in a Visual Studio it is possible to commit that solution to a source control repository

  • Provisioning Infrastructure – Rapid Tools Provisioning

    • Provisions default site structure and content from a SharePoint Feature

    • XML definition file for content import

    • Pluggable architecture to support any custom asset

  • Isolated environment s

    • Solution is deployed via wsp, all customization are deployable in one package

    • Site collection is provisioned from scratch for each environment

  • Continuous Integration

    • Because of the points above continuous integration is possible

    • Allows you to pull a build at anytime for deployment to test or for release

  • Read more: http://www.ascentium.com/blog/sp/Post71.aspx



Q & A

  • Visit http://rapid-tools.googlecode.com for more information

  • Future enhancements:

    • SPDeploy Visual Studio Addin

    • User Profiling

    • Windows LiveID and Forms Auth providers

    • Exception display


ad