[I sent this to my team today, and thought it would make a good post as well.]
I’ve been meaning to do this for awhile, and now that I have the chance – I’d thought I’d give everyone a backgrounder on [SharePoint 2003 Ghosting] issue. Also, following the backgrounder you’ll find further links on Ghosting & SharePoint 2007 (which is scheduled to hit Q2 2006 – rumors say this month).
More info on what [Ghosting] is, and what it means from a SharePoint perspective: http://www.awprofessional.com/articles/article.asp?p=454785&seqNum=4
As this article notes, any pages that are changed with FrontPage are unghosted. Even if you save the changes off to a template – the unghosted pages remain unghosted in all sites that use that template.
Unfortunately this article (based on a book that was just released, does not take into consideration using Windows SharePoint Services SP2 and ASP.NET 2.0 (and for us Son of SmartPart to host ASP.NET 2.0 UserControls). WSS SP2 has some issues when you modify a page with SharePoint (this action by default unghosts a page). Essentially the modified page breaks various WSS functions (as noted by Brad Smith, an MVP SharePoint: http://msmvps.com/blogs/brad/archive/2006/02/21/84440.aspx) [Brad - you still owe me lunch. :) ]
For further reading on Ghosting:
Ghosting and ReGhosting
Ghosting Schmosting
Ghosted and unghosted pages (the MSFT guy who is responsible)
Ghosted vs. Unghosted (read the #1 reason not to unghost pages)
Regarding Office SharePoint Portal 2007:
Office 2007 in October? (2006)
What’s Coming in WSS “v3.0”
Prepare yourself for SharePoint 2007 - Learn ASP.NET 2.0 Now
SharePoint 2007 Product Guide
Office SharePoint Server 2007 and Office SharePoint Designer 2007
SharePoint Designer 2007 Features
Update [8/14/2006]: Fixed broken links. Thanks Tom.
posted @ Wednesday, April 12, 2006 10:27 AM