Monday, April 14, 2008
Wednesday, April 9, 2008
Advanced scenario for SharePoint Blog site template - Sharepoint Use Cases
Advanced scenario for SharePoint Blog site template - Sharepoint Use Cases
When is a blog not a blog? When it's "News" -- with some nifty changes to make headlines more effective when displayed on the parent site home page.
When is a blog not a blog? When it's "News" -- with some nifty changes to make headlines more effective when displayed on the parent site home page.
Tuesday, April 8, 2008
An Introduction to Conditional Formatting
Microsoft SharePoint Designer Team Blog : An Introduction to Conditional Formatting
Using SharePoint Designer to manage hide/show or colors based on data conditions. Behind the scenes, uses XSLT.
Using SharePoint Designer to manage hide/show or colors based on data conditions. Behind the scenes, uses XSLT.
Building a SharePoint Designer Mashup (Part 1)
Microsoft SharePoint Designer Team Blog : SharePoint Conference - Building a SharePoint Designer Mashup (Part 1)
Using SPD's Data View to combine information from different lists (and other sources). Includes a fixup for filtering on lookup-type fields.
Using SPD's Data View to combine information from different lists (and other sources). Includes a fixup for filtering on lookup-type fields.
SharePoint - Firefox and NTLM authentication
SharePoint - Firefox and NTLM authentication
Gives a workaround to let Firefox provide windows credential automatically to trusted hosts when used from intranet clients
Gives a workaround to let Firefox provide windows credential automatically to trusted hosts when used from intranet clients
Chris O'Brien's blog: Blending publishing/collaboration functionality in SharePoint
Chris O'Brien's blog: Blending publishing/collaboration functionality in SharePoint: "Use of Content Editor web parts vs publishing RichHtmlField controls
Most folks in WCM development know there is an overlap in functionality provided by the Content Editor web part and the RichHtmlField control in the Microsoft.SharePoint.Publishing.WebControls namespace, i.e. they can both be used to enter page content such as text/images. However it's important to consider the differences - the RichHtmlField control stores it's content in a column of the list item for the page, whereas the CEWP is a web part and thus stores content in the web part storage architecture. This is important, since if deployment to a different environment is in your project plan or ongoing architecture, things will likely be simpler if you use the field control, since this content will then travel with the page properly.
Additionally, there are some URL fix-up issues with using the CEWP across different environments, as documented in the HawaiianAir.com write up.
In summary, I'd recommend considering the CEWP as a means of entering content in non-publishing SharePoint sites only."
Most folks in WCM development know there is an overlap in functionality provided by the Content Editor web part and the RichHtmlField control in the Microsoft.SharePoint.Publishing.WebControls namespace, i.e. they can both be used to enter page content such as text/images. However it's important to consider the differences - the RichHtmlField control stores it's content in a column of the list item for the page, whereas the CEWP is a web part and thus stores content in the web part storage architecture. This is important, since if deployment to a different environment is in your project plan or ongoing architecture, things will likely be simpler if you use the field control, since this content will then travel with the page properly.
Additionally, there are some URL fix-up issues with using the CEWP across different environments, as documented in the HawaiianAir.com write up.
In summary, I'd recommend considering the CEWP as a means of entering content in non-publishing SharePoint sites only."
Subscribe to:
Posts (Atom)