I often work with and train technical staff on how to administrator, develop on, and apply customizations/branding to SharePoint. One topic that always seems to be tough to grasp is the concept of ghosted and unghosted files in SharePoint. Whenever I'm branding SharePoint, I have always unghosted (modified SharePoint files, thus having them be persisted) files and wasn't overly concerned about potential performance hits.
I think there are two camps who are concerned about unghosting: 1) Those that are used to working with files, and find it odd that some files are now persisted in SharePoint, and 2) those that believe that there is a performance loss via unghosted files.
Joel Oleson mentions says that he would argue that unghosted pages actually perform better. My stance is to avoid unghosting if you can, but if you need to do it, do it. Heck, you might even get a performance gain. If somthing goes wrong, you can reset to the site definition and start over.
When it comes to core.css, unghosting doesn't just affect performance, it affects the ordering of css files. There are a number of ways to affect when core.css gets loaded in comparison to your custom styles, but I wont get into that here. If you don’t want to create a link to an alternate css file at the end of core.css (and thus forcing the unghost), I like this solution by Michael Hofer. Its clean and no ghosting, but I still ain’t afraid of no ghost.
PS - here's what really happens when you unghost... (DB level explanation of sharepoint unghosted files) http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=4
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5
After doing some research on psconfig and stsadm for SP configuration automation, I found a great post (special thanks to paul horsfall), which gave me a good start. Yet I was getting errors because some of the required services wern't running (i.e wss help search, moss search, excel calc services). So. I wrote this batch script to configure SharePoint on development machines, and it worked on the vmware machines that I'm deploying. Using a script like this is much better than an attended install via the config wizard and then jumping around to different in central admin and SSP to set everything up. Replace USERNAME, PASSWORD, EMAIL where appropriate. If anyone has additions or refinements, please let me know!
PS check out this page for more information on template types... http://blogs.msdn.com/dwinter/archive/2006/07/07/659613.aspx
_________________________________________________
@echo off
REM configures sharepoint for first time use
echo.
:1.configdb, admin site
cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN"
psconfig -cmd configdb -create -server %COMPUTERNAME% -database SharePoint_Config -user USERNAME -password PASSWORD
:2.helpcollections
psconfig -cmd helpcollections -installall
:3.secureresources
psconfig -cmd secureresources
:4.services
psconfig -cmd services -install
:5.installfeatures
psconfig -cmd installfeatures
:6.adminvs
psconfig -cmd adminvs -provision -port 8080 -windowsauthprovider onlyusentlm
:8.applicationcontent
psconfig -cmd applicationcontent -install
REM configuration wizard equilivant complete, start other tasks
:turn on services
stsadm -o spsearch -action start -farmserviceaccount USERNAME -farmservicepassword PASSWORD
stsadm -o osearch -action start -farmserviceaccount USERNAME -farmservicepassword PASSWORD -farmcontactemail EMAIL -role IndexQuery
STSADM.EXE -o provisionservice -action start -servicetype "Microsoft.Office.Excel.Server.ExcelServerSharedWebService, Microsoft.Office.Excel.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
:echo Creating webapps for SSP
stsadm -o extendvs -url http://%COMPUTERNAME%:90 -ownerlogin USERNAME -owneremail EMAIL -exclusivelyusentlm -apidname "SSP - 90" -apcreatenew -apidtype configurableid -apidlogin USERNAME -apidpwd PASSWORD
stsadm -o extendvs -url http://%COMPUTERNAME%:99 -ownerlogin USERNAME -owneremail EMAIL -exclusivelyusentlm -apidname "My Sites - 99" -apcreatenew -apidtype configurableid -apidlogin USERNAME -apidpwd PASSWORD
iisreset
echo Creating SSP
stsadm -o createssp -title "Shared Service Provider" -url http://%COMPUTERNAME%:90 -mysiteurl http://%COMPUTERNAME%:99 -indexserver %COMPUTERNAME% -indexlocation "%Programfiles%\Microsoft Office Servers\12.0\Data\Applications" -ssplogin USERNAME -ssppassword PASSWORD
REM using pub portal template, for more go to http://blogs.msdn.com/dwinter/archive/2006/07/07/659613.aspx
echo Creating site collection on port 80
stsadm -o extendvs -url http://%COMPUTERNAME%:80 -ownerlogin USERNAME -owneremail EMAIL -exclusivelyusentlm -apidname "SharePoint - 80" -sitetemplate BLANKINTERNET -apidtype configurableid -apidlogin USERNAME -apidpwd PASSWORD
iisreset
pause
Currently rated 3.3 by 4 people
- Currently 3.25/5 Stars.
- 1
- 2
- 3
- 4
- 5