Microsoft SharePoint and .NET Technology Insight

SharePoint, .NET, Office365, Windows Azure, TFS, Project Server and SQL Server Technology Insights


1 Comment

SharePoint 2013 and Responsive Web Design (RWD)

Responsive Web Design (RWD) pushes a client-side solution resulting from a combination of JavaScript and CSS and presenting an entirely different page structure to different devices, with some original elements hidden or moved around. RWD involves the use of a variety of grids in the page layout and CSS media queries. The use of media queries provides a flexible design because it moves to the browser the burden of switching on the proper cascading style sheet whenever the size of the window matches one of the provided media types.

SharePoint Server 2013 offers new, optimized viewing experiences across different mobile platforms including a new way for designers to design a site once, and then based on that design render it using different Style Sheets and Master Pages, multiple times.

Resources on Device Channels:

http://blogs.technet.com/b/christwe/archive/2012/11/02/sharepoint-tidbit-sharepoint-2013-device-channels.aspx
http://msdn.microsoft.com/en-us/library/jj862343.aspx
http://blogs.perficient.com/microsoft/2012/07/mobility-in-sharepoint-2013-device-channels/

Device Channels look very promising for many users of SharePoint but with the need to create and maintain multiple interfaces for Device Channels to work well, and the fact that there are new mobile devices every month with different screen resolutions, Responsive Design still is the way to go as Eric Overfield points out in this blog posting:

http://blog.pixelmill.com/1291/responsive-web-design-for-sharepoint-2013-and-sharepoint-2010/

Eric has done some phenomenal work to create a Codeplex solution for modifying a popular responsive design framework namely Twitter Bootstrap. The goal of this project is to provide popular grid and responsive frameworks converted to SharePoint 2010 and SharePoint 2013.

http://responsivesharepoint.codeplex.com/


Leave a comment

SharePoint 2010 and Host Named Site Collections

A host header is a third piece of information that you can use in addition to the IP address and port number to uniquely identify a Web domain or, as Microsoft calls it, an application server. In SharePoint 2010, host headers can be applied at two different levels :

The Web application (IIS Web site) level
The site collection level

A host-named site collection allows you to address a site collection with a unique DNS name. A SharePoint Web Application when created contains many path-based site collections that share the same host name (DNS name). For example, Team A has a site collection at http://abc.com/sites/teamA, and Team B has a site collection at http://abc.com/sites/teamB. These are referred to as path-based site collections, and is the recommendation for most corporate scenarios. Host named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as http://TeamA.abc.com and http://TeamB.abc.com allowing for scalability. This is a feature of SharePoint that allows individual site collections to have their own top-level URL.

The following code snippet programmatically creates the host-named site collection with the URL https://sharepointzen.wordpress.com in the SharePoint Server 2010 Web application with the URL https://sharepoint

SPWebApplication webApp = SPWebApplication.Lookup(new Uri("http://sharepoint"));
SPSiteCollection sites = webApp.Sites;
SPSite Site = sites.Add(“https://sharepointzen.wordpress.com”, "Test",
"Test Site", 1025, "STS#0", "domain\abc","Arshad Riz", “ariz@test.com”, "domain\abc1”,"Ak Riz", akriz@test.net, true);

PowerShell can also be used in place of server object model code. Please refer to : http://technet.microsoft.com/en-us/library/cc424952.aspx