There are several solutions in web that deal with this problem, but they all seem to point you to use SPWebConfigModification (like in here and here) or are just giving manual editing instructions (like in here). We feel that this is all too complex and repetitive process. There is fortunately “a better” way to…
Read more »
UPDATE:
My colleague, Lauri, went further after we discussed the method described in this article, and he generalized the process of making Visual Web Parts. I really like his approach more, as it also solves the problems with web part connections and the “double refreshing” problem, so please consider this article as obsolete and look at the better…
Read more »
There is sometimes a need to copy files in a SharePoint farm on different locations, than what can be specified in wsp-packages. Usually the best way to do it farm-wide, is to use Features and timer jobs. Timer jobs can be specified so that they are executed on every single machine in a SharePoint farm. In SharePoint 2007 the most…
Read more »
If you are working with SharePoint 2010, see this article by Todd Carter:
An Expected Error Has Occurred
Mike has also written a nice article of the other options:
SharePoint 2010 Custom Error Messages for Public Facing Deployments
SharePoint doesn’t have an out-of-the-box support for custom error pages. Or at least it’s a little bit problematic to implement custom error pages…
Read more »
This is rather uncommon situation, but we needed a way to easily translate strings in our code against the resources deployed in 12\Resources. We created extension methods for that:
public static string Localize(this string source)
{
return Localize(source, (uint) Thread.CurrentThread.CurrentCulture.LCID);
}
…
Read more »
SharePoint’s out-of-the-box breadcrumb control is kinda a strange animal. Basically you have three different kinds of breadcrumbs in SharePoint. Each of these breadcrumbs are using different provider for their back-end:
- Layout Pages / Administration Pages use SPXmlContentMapProvider,
- Publishing Pages use CurrentNavSiteMapProviderNoEncode, and
- Form Pages (AllItems.aspx, EditForm.aspx, DisplayForm.aspx, etc.) use SPContentMapProvider
This is all fine, when you have different master…
Read more »