SharePoint is an information solution described by Microsoft as “The Business Collaboration Platform for the Enterprise and the Web”.
On 12.21.09, In 3 General, By J. Chris Gibson
On 11.16.09, In 2 Microsoft Technologies, By J. Chris Gibson
I am excited about customizing and branding capabilities in SharePoint 2010. The number of CSS files in SharePoint 2010 has increased from SharePoint (WSS 3) dramatically, so site branding using custom styles has become somewhat more complex, but the fundamental concepts and branding procedures are the same.
There is greater flexibility in using the application.master page for customizing your site — from the 2009 SharePoint conference: “An upgrade site can then exist in one of three states: Office SharePoint Server 2007, SharePoint 2010 preview mode, and SharePoint 2010. This allows the site administrator the ability to first view the site with the SharePoint 2010 user interface before committing to it.” Also in WSS 3, having your custom CSS load last after core.css was a challenge. In SharePoint 2010 there is an “After” property in <SharePoint:CssRegistration> that you use to direct the CssRegistration tag to which CSS file you want loaded after core.css. Code like this:
<SharePoint:CssRegistration name=”custom.css” After=”corev4.css” runat=”server”/>
Nice eh?
There are many other features and capabilities like the ability to ad favicons, more browser variety including automatic support for mobile device browsers, a property (UseSimpleRendering) for simple page rendering, and more.
On 11.10.09, In 1 Our Products, By J. Chris Gibson
FramEx Pro™ is a library of funcitons that extend elements of the Microsoft® .NET framework including System.Web, Cryptography, Reflection, data access, and more. We have created framework extension components for each of these .NET Framework components separately in various customer projects, and soon we will release them to the general public in an aggregate package called FramEx Pro™ 1.0 .
On 06.28.09, In 2 Microsoft Technologies, By J. Chris Gibson
Development in WSS involves deployment of custom source files into the WSS \TEMPLATE folder. In Visual Studio it is helpful to create a project with a folder structure that reflects the \TEMPLATE folder to automate moving source files to the deployment location.