Eli Robillard's World of Blog.
Bligger. Blagger. Blogger.
-
Building and Packaging SharePoint Solutions
In my last post I described a strategy for: Planning SharePoint Solution Packages. In this post we'll construct a sample solution template, use that template to construct a real solution, package this as a WSP, and finally (once you have many WSPs) wrap the entire process with a routine to automate the build. You can download the sample code from the WSPSolution project on CodePlex. Let's get started.
-
Toronto SharePoint User Group Wednesday, July 15: Feature Sets and Alerts
-
Toronto SharePoint Saturday coming up July 11, 2009
If you haven’t registered yet for Toronto SharePoint Saturday then you ONLY have a couple days left until the event.
The schedule has been posted on the site and can be downloaded directly: SPS TO Schedule.
Join SharePoint architects, developers, and other professionals that work with Microsoft Office SharePoint Server 2007 for Toronto's SharePoint Saturday, on July 11, 2009 at Microsoft Canada on 1950 Meadowvale Blvd in Mississauga, Ontario, Canada. SharePoint Saturday will be an educational, informative & lively day filled with sessions by respected SharePoint professionals and MVPs, covering a wide variety of SharePoint-related topics. SharePoint Saturday is FREE, open to the public and is your local chance to immerse yourself in SharePoint! -
Eli's SharePoint 2007 Resources
What's Here
-
Planning SharePoint Solution Packages (WSPs)
SharePoint architects and developers often wonder how best to design solution packages for long-term ease of use, especially through upgrade cycles. In a survey of SharePoint developers I found a range of strategies from one monolithic WSP to hold everything, up to practically one per feature which resulted in as many as 50 WSPs for a project. The variance depended on the developer's goals for maintenance. Application vendors want to keep things simple for admins, so a single solution per product makes sense. When downtime needs to be absolutely minimized and you need absolute granular control over each and every feature, maybe you want to maintain dozens of packages so that upgrading one will minimally affect the others.
-
Toronto SharePoint User Group: May 27 and June 17
This is a heads-up about two exciting TSPUG sessions coming soon: next week on May 27 and next month on June 17.
-
Preview: The practical limits of people and SharePoint
-
TSPUG Tonight: Workflow, K2 and Twitter
Attendees of the Wednesday March 25 edition of the Toronto SharePoint User Group will navigate the wonders of Document Life Cycle in SharePoint using K2 BlackPearl. Our own Bill Brockbank will verily demonstrate how K2 can be used to manage the governance, authoring and editing of a document library with nothing up his sleeves except K2's BlackPearl. From there Bill will reveal the magic of multi-level approval before deeming a work as final and published. Magical stuff indeed.
-
First Looks: Visual Studio 2010 tooling for SharePoint
Via Soma: Sharepoint tools support in Visual Studio
http://blogs.msdn.com/somasegar/archive/2009/02/19/sharepoint-tools-support-in-visual-studio.aspx
In the screenshots, note the .package and .feature files, as well as the Packaging Explorer tab on the right. In the example a feature is displayed where there are several elements available in the solution (left), with just the workflow features being selected into “Workflows.feature” (right). -
Reminder TSPUG Tonight: SharePoint Solutions and Automating the Build
The topic for tonight was suggested during the most recent Toronto SharePoint camp - How to structure SharePoint solutions in Visual Studio, and automate the build and WSP generation. Building SharePoint Solutions (WSP) is the most painful part of the development process. In this session attendees will learn how to take the pain away for SharePoint 2007 by structuring Visual Studio Solutions for easy management, and by automating the build and WSP creation.