Here we summarize a number of best practices for developing SharePoint solutions.
E. Wilansky, T. Stojecki, P. Olszewski and S. Kowalewski
MSDN Magazine March 2009
View Complete Post
SharePoint 2010 introduces a number of new ways to access business data and present it to the user. We'll show you several options that range from no-code solutions to fully integrated Office add-ins.
Donovan Follette , Paul Stubbs
MSDN Magazine July 2010
The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.
MSDN Magazine November 2009
Microsoft Office SharePoint Portal Server 2003, which is part of the Office System, lets you create and manage virtual servers, site collections, sites, workspaces, and users. You can also use the Windows SharePoint Services object model to design and implement user-targeted applications. In the second part of a two part series, the authors take a look at the WSS and SPS object models, Web Part Page anatomy, creating and deploying Web Parts, and Web Part security. They also discuss Web Part infrastructure and how to create custom Web Parts.
Jason Masterman and Ted Pattison
MSDN Magazine August 2004
In this article the authors provide an in-depth examination of the architecture of SharePoint products and technologies: WSS and SPS. WSS provides the foundation for creating collaborative Web sites that support customization and personalization and SPS complements WSS by playing the role of a content aggregator. This article explains how.
MSDN Magazine July 2004
I'm currently busy with an overview of Best Practices for developing accessible web sites in SharePoint 2007. After a little research I have noticed that the challenges I have faced so far are mostly XHTML/CSS/JS related and there are actually very few SharePoint 2007 specific issues: this has to do with the fact that we use very little to none of standard SharePoint controls in the Internet facing web sites we deliver.
As I would like to share the Best Practices I'm writing with the community I've been wondering whether you have tried to develop an accessible web site in SharePoint 2007 yourself and faced any challenges you would like to share. To make myself clear I'm looking for issues and challenges and not solutions in particular (these are welcome as well by the way).
Recently I've been busy with a research on accessibility of Web Content ManagementÃÂ solutions based on SharePoint 2007. My outcome is: SharePoint 2007 WCM solutions can be accessible and depending on the approach you canÃÂ score up to 95% WCAG 1.0 Priority 2.0 compliancy without any toolkit.
I've been wondering whether anybody else shares my opinion or has his/her own...