You are currently browsing the category archive for the ‘SharePoint’ category.

As you’ve probably seen by now, once you create multiple site collections in the same web application, you don’t get a lot of options as far as database location. Well, it’s really not that complicated:

  • Create the databases for the new site collections (easy enough in CA)
  • Run the following PowerShell command for each site collection, or put it in a script if you feel like it:

Move-SPSite <YourSiteURL> –DestinationDatabase <ContentDBName>

That’s it, easy as pie. See more information on TechNet:

http://technet.microsoft.com/en-us/library/cc825328.aspx

Enjoy!

Part of SharePoint 2010, a new tool was added to made life easier: the developer dashboard. By default disabled, you can enable it multiple ways:

Using STSADM:

stsadm –o setproperty –pn developer-dashboard –pv ondemand

Using PowerShell:

$level=”OnDemand”

[void][System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)

[void][System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint.Administration”)

$contentSvc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService

$contentSvc.DeveloperDashboardSettings.DisplayLevel=([Enum]::Parse([Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel],$level))

$contentSvc.DeveloperDashboardSettings.Update()

Write-host(“Level:” + $contentSvc.DeveloperDashboardSettings.DisplayLevel)

Values available to be set for the developer dashboard:

  • On
  • Off
  • OnDemand

Using code:

SPWebService srv = SPWebService.ContentService;

srv.DeveloperDashboardSettings.DisplayLevel = SPDeveloperDashboardLevel.OnDemand;

srv.DeveloperDashboardSettings..Update();

NOTE: using SPFarm is not supported in the final release of SharePoint.

Happy debugging!

Ok, this should be common knowledge by now, but when setting your own development box for SharePoint (whether it’s 2007 or 2010), these are the changes to web.config required to show proper error messages, and none of that “friendly” end-user centric messages:

<configuration>

<SharePoint>

<SafeMode CallStack=”true” … />

</SharePoint>

<system.web>

<CustomErrors mode=”off” />

</system.web>

</configuration>

 

Other sources to look at when debugging:

  • SharePoint event log
  • SharePoint logs
  • Debug the working process
  • IIS logs
  • Use tracing
  • Use remote debugging if no debugger is installed (not usually applicable to your development box)

This is not something I do every day, and I keep forgetting how to do it, so I’m posting this as a self-reminder.

On a Publishing site (collection), if I need to add sub-sites based on the Team Site template:

Go to Site Settings > Look and Feel > Page Layouts and Site Templates

Add from there the Team Site or any other site template to be used

Go and create a new sub-site based on the template just added.

Enjoy!

Because I’ve been asked so many times what’s the difference between the versions, and what’s included at what level, here’s the official list of features by version:

http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-Comparison.aspx

Also, a good list, same thing but different layout:

http://thecommunicator.co.cc/2010/05/03/sharepoint-2010-feature-comparison-sharepoint-foundation-2010-vs-sharepoint-2010-standardenterprise/

Enjoy!

MVP Reconnect

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 617 other followers

Follow Dynamics 365 Wizardry on WordPress.com