Showing posts with label
Programmatically create a host-named site collection.
Show all posts
Showing posts with label
Programmatically create a host-named site collection.
Show all posts
In addition to using the Windows PowerShell to create host-named sites, you can use the SharePoint Server 2010 object model. The following code sample creates the host-named site collection with the URL
http://host.header.site.url in the SharePoint Server 2010 Web application with the URL
http://servername:
Popular Posts
-
This is the method, I followed to achieve – add image to custom list with calculated / conditional column. Following is the result list...
-
if you want to do a User profile import in SharePoint 2010.. you should have the 'User Profile Synchronization Service' started....
-
SharePoint provides you “Export to Spreadsheet” feature across almost all list, allowing you to export your list content to Excel. But no...
-
Note: A LOT of these questions are specific to SharePoint 2007, and won't have applicability for SharePoint 2003! 1) What are the...
-
A very common & known issue while migrating IE versions. There is couple of steps and checking should be done to get this resolved. ...
-
I found this really great article that talks in depth as well in an easy language about the new options of under look and feel of 2013. h...
-
The April 2015 Cumulative Update for SharePoint 2010 has been released. SharePoint Foundation: https://support.microsoft.com/en-us/kb...
-
We love virtual labs they are free, non hassle and disposable ways to work around SharePoint deployment SharePoint 2010 virtual lab can be...
-
The April 2015 Cumulative Update for SharePoint 2013 has been released. SharePoint Foundation: http://support.microsoft.com/kb/29652...
-
June 2014 Cumulative Update for SharePoint 2013 has been released. SharePoint Foundation - KB2881063 http - //support.microsoft.com/kb...
Disclaimer
The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.
