David Chappell

  • September 2020
  • November 2017
  • April 2017
  • October 2016
  • March 2016
  • February 2016
  • August 2015
  • April 2015
  • December 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • December 2004
  • November 2004
  • October 2004
  • September 2004
  • August 2004
  • July 2004
  • June 2004
  • May 2004
  • April 2004
  • March 2004
  • February 2004
  • January 2004
  • December 2003

Opinari

Get the Feed! Subscribe

The SharePoint 2010 Developer Platform  
# Tuesday, October 27, 2009
 
The popularity of SharePoint continues to amaze me. It's a useful technology, so I'm not surprised that people like it. What I marvel at is how rapidly it's spread. Are there any Windows customers left who aren't using it in some way?

SharePoint is a platform for building applications as well as an application itself, but its platform aspect hasn't gotten as much attention. At least in part, this is because the SharePoint development environment hasn't been as easy for .NET developers to use as it might have been.

Yet a SharePoint app is fundamentally an ASP.NET app, so the two worlds have a good deal in common. With the 2010 release, Microsoft has put a significant amount of effort into making SharePoint a better development platform for creating what might otherwise be straight ASP.NET applications.

If you're interested in this area, I've written a Microsoft-sponsored white paper titled The SharePoint 2010 Developer Platform: An Introduction for ASP.NET Solution Architects. The paper's goal is to provide a big-picture view of SharePoint as a platform for creating applications. It's clear to me that with the advent of SharePoint 2010, a significant number of applications that might have been built using plain ASP.NET will instead be built on SharePoint. If you're interested in why, you might find the paper useful.


10 comments :: Post a Comment

 


Comments:

While SharePoint will be a good platform for developing collobration type apps I believe the next killer platform for LOB apps from MS is what they are coining XRM, which is based on MS CRM today.

http://blogs.zdnet.com/microsoft/?p=1321
 

xRM certainly has lots of potential. From a cloud platform perspective, it would be a direct competitor to Force.com, offering a similar kind of service but without the cloud lock-in (since there's an on-premises version of xRM, too).

Still, I'd argue that Microsoft isn't promoting xRM as a mainstream platform yet. I'd also argue that the SharePoint platform is closer to .NET than xRM, so it's a more natural fit for most Windows developers today. Finally, the installed base of SharePoint is much larger than that for Dynamics CRM, the home of xRM. Given all of these things, I'm expecting lots more new apps to be built on SharePoint in the next couple of years than on xRM.
 

These are some great insights into the rapid spread of SharePoint in the workplace. I am looking forward to reading your paper and will pass it along to my SharePoint developer friends. Keep up the great posts!

You should also consider joining the SharePoint conversation at http://www.facebook.com/office

Cheers,
Andy
MSFT Office Outreach Team
 

Dave I've read your white paper, I'd actually written a post before reading this here for SP2010:
http://www.sharepointdevwiki.com/display/sp2010/2009/11/04/The+12+factors+to+turn+ASP.NET+developers+to+SharePoint+2010
and had also written one for SP2007 too here:
http://www.sharepointdevwiki.com/pages/viewpage.action?pageId=7340352

Be interested on your comments on both.
 

Your post is really interesting, Jeremy--thanks very much for pointing me at it. 2010 looks like a watershed moment for SharePoint developers.
 

I admire David Chappell, I really do. This paper reflects his trademark precision, clarity and integrity. I’m sure that’s why Microsoft funded it. This is a large and important topic, and David’s short paper is a worthy contribution. But it’s incomplete and potentially misleading. I get the feeling he did not talk to all the right people. Probably not architects who have spent years making SharePoint work as a platform in a mid-sized IT department in a Fortune 250 company, like me. If I can make the time, I will write up a full response and try to identify the missing pieces (though I’m not sure whether I should try to share it outside my company). In the meantime, I’m concerned that pointy haired decision makers will not detect the ambivalence that I see in David’s concluding paragraphs. If his article is SharePoint’s resume that wins it a full interview, that’s good. If it is an unqualified offer of employment, something’s wrong. Ironically, my Sunday morning reading of the article was interrupted by a call. “SharePoint is down.”
 

Thanks for the kind words, Anonymous. To me, though, the paper is full of caveats, down to explicitly stating what kinds of apps SharePoint is and isn't intended for. My goal was absolutely to win SharePoint an interview, to help ASP.NET solution architects think more clearly about when building on SharePoint could make their lives better. I'm certainly not arguing that all ASP.NET apps should really be SharePoint apps.

And server farms running ASP.NET also go down from time to time.
 

Thank you for the good post, I agree with most of your points.Great posts, loved reading it, thanks!
 

Nice article..........
 

SharePoint 2010 offers a better development platform and probably faster search capabilities as well.
 

Post a Comment


<< Home