OneNote Table Of Contents Add-in

http://blogs.msdn.com/b/johnguin/archive/2011/04/28/updated-the-onenote-table-of-contents-and-sorter-powertoy.aspx

Sitecore Firebug Javascript Error

Using IE8 with Sitecore there is sometimes a javascript error that has to do with a firebug lite item that Sitecore has embedded into the designer. To get rid of firebug lite and thus the error, do the following.

Open the Core database, navigate to /sitecore/layout/Devices/Internet Explorer and delete the Firebug Lite item.

This information originally comes from a Sitecore developer.

http://stackoverflow.com/questions/2513586/is-firebug-lite-javascript-must-need-in-sitecore-shell

SharePoint 2010 Site Templates Document Library Workflow + OneNote

I ran across a strange problem today. Here's my situation. Saving a site as a site template (wsp solution), the site had a document library that had a default template of a OneNote file and it also had workflow associated with it (created with SPD). Using the site template to recreate the file works but the document library's "New Document" button was disabled and there was no template associated with it in the new site.

I wrote a bit of code that resets the document library to use the OneNote document as its template but the question remains, why did that button get greyed out when a workflow was associated with that document library and saved in the template.

I tested saving the template without the workflow associated with the document library and the OneNote template stayed associated with the document library, it was only when I associated a workflow with the document library that the "New Document" button got greyed out.

Bug!

OneNote Publish to PDF

Microsoft.Office.Interop.OneNote Publish. To publish the entire notebook, use the code below, where Personal is the name and folder of my notebook. The Publish action will find all the .one files and combine them into one pdf file. Whammooo!!

var onenoteApp = new Microsoft.Office.Interop.OneNote.Application();

string bstrHierarchyID = string.Empty;

onenoteApp.OpenHierarchy(@"C:\Users\brad.test\Documents\OneNote Notebooks\Personal\",

System.String.Empty, out bstrHierarchyID, Microsoft.Office.Interop.OneNote.CreateFileType.cftNone);

string bstrTargetFilePath = "C:\\Temp\\Personal1.pdf";

onenoteApp.Publish(bstrHierarchyID, bstrTargetFilePath, OneNote.PublishFormat.pfPDF);

SharePoint EditControlBlock RegistrationId types

public enum SPListTemplateType
{
InvalidType = -1,
GenericList = 100,
DocumentLibrary = 101,
Survey = 102,
Links = 103,
Announcements = 104,
Contacts = 105,
Events = 106,
Tasks = 107,
DiscussionBoard = 108,
PictureLibrary = 109,
DataSources = 110,
WebTemplateCatalog = 111,
UserInformation = 112,
WebPartCatalog = 113,
ListTemplateCatalog = 114,
XMLForm = 115,
MasterPageCatalog = 116,
NoCodeWorkflows = 117,
WorkflowProcess = 118,
WebPageLibrary = 119,
CustomGrid = 120,
DataConnectionLibrary = 130,
WorkflowHistory = 140,
GanttTasks = 150,
Meetings = 200,
Agenda = 201,
MeetingUser = 202,
Decision = 204,
MeetingObjective = 207,
TextBox = 210,
ThingsToBring = 211,
HomePageLibrary = 212,
Posts = 301,
Comments = 302,
Categories = 303,
IssueTracking = 1100,
AdminTasks = 1200,
}

SharePoint 2010 Backward Compatible Document Library Events

They still work. Hooray!!

When I go to the SharePoint 2010 document library settings I can see:

Specify the assembly name, class name and properties for the document library's event handler. WSS_LONG_NAME will call this event handler when items in the document library are inserted, updated, or deleted.

Not sure what "WSS_LONG_NAME" is but apparently it will call my SharePoint 2010 document library event handler.

To enable this to show, I went to Central Admin of my SharePoint 2010 farm, Manage Web Applications, select the web application and then click on Resource Throttling. There will be a radio button to turn this (backward compatible document library events) on or off.

SharePoint 2010 Common Navigation Across Site Collections

So Microsoft best practice dictates content dbs should be less than 100GB or so, at least that's what I think. Either way, you're here because you have multiple site collections and want to know how to have the same top navigation bar across all the site collections. It took me a few hours to find but here's the solution.

In web.config file, add the following provider


<siteMap defaultProvider="CurrentNavigation" enabled="true">

<providers>

<add name="CustomTopNavProvider" siteMapFile="/_layouts/1033/CustomTopNavMenu.sitemap" type="System.Web.XmlSiteMapProvider,System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>




Add the CustomTopNavMenu.sitemap to the 1033 directory. If you don't know how to create or use a sitemap file just google it.

Open up the master page for each site collection, for 2010 it's v4, probably best to create a copy and all that stuff before editing it.

Find this part of the file. (around line 343)


<SharePoint:AspMenu

  ID="TopNavigationMenuV4"

  Runat="server"

  EnableViewState="false"

  DataSourceID="topSiteMap"

  AccessKey="<%$Resources:wss,navigation_accesskey%>"

  UseSimpleRendering="true"

  UseSeparateCss="false"

  Orientation="Horizontal"

  StaticDisplayLevels="2"

  MaximumDynamicDisplayLevels="1"

  SkipLinkText=""

  CssClass="s4-tn"/>

<SharePoint:DelegateControl runat="server" ControlId="TopNavigationDataSource" Id="topNavigationDelegate">

<Template_Controls>

<asp:SiteMapDataSource

  ShowStartingNode="False"

  SiteMapProvider="SPNavigationProvider"

  id="topSiteMap"

  runat="server"

  StartingNodeUrl="sid:1002"/>

</Template_Controls>

</SharePoint:DelegateControl>





and change it to the following:


<SharePoint:AspMenu

  ID="TopNavigationMenuV4"

  Runat="server"

  EnableViewState="false"

  DataSourceID="topSiteMap"

  AccessKey="<%$Resources:wss,navigation_accesskey%>"

  UseSimpleRendering="true"

  UseSeparateCss="false"

  Orientation="Horizontal"

  StaticDisplayLevels="1"

  MaximumDynamicDisplayLevels="4"

  SkipLinkText=""

  CssClass="s4-tn"/>

<SharePoint:DelegateControl runat="server" ControlId="TopNavigationDataSource">

<Template_Controls>

<asp:SiteMapDataSource

  ShowStartingNode="False"

  SiteMapProvider="CustomTopNavProvider"

  id="topSiteMap"

  runat="server"

/>

</Template_Controls>

</SharePoint:DelegateControl>





basically we are setting the SiteMapProvider to the provider we added in the web.config that reads our custom site map file. We don't show the starting node, we remove an ID of the DelegateControl (may or may not be necessary) and then set the StaticDisplayLevels of the ASPMenu to 1 and the MaximumDynamicDisplayLevels to 4. S

Save masterpage, reload page and whamooo, it should work. If not, leave a comment and I'll try to help.

Expanding on this, if you created a web part that could read and update the sitemap file, then users would not necessarily need access to the 1033 folder to update navigation.

UPDATE: after some research, it doesn't seem possible to dynamically update the .sitemap file using a web part. I suggest putting a custom folder in the 1033 folder for navigation and share it out to those who need to be able to update it. It will need to be update on all front end web servers.

SQL Reporting Keep Header Rows Visible Repeat on New Page

This shouldn't be that difficult to figure out. But it is, so here is how to do it.

Select the first static member of the Tablix and set the property of RepeateOnNewPage to True and the KeepWithGroup property to After.

That's it.

How to set focus on textbox within ModalPopUp Extender Panel

Taken from: http://forums.asp.net/t/1218079.aspx

javascript
function pageLoad(){
$find("ModalPopupExtender's BehavoirID").add_shown(onModalPopupShown);
}
function onModalPopupShown(){
//set focus here.
}

javascript end

SharePoint Service Pack 2 Expiration Date Hot Fix Available

http://support.microsoft.com/default.aspx?scid=kb;EN-US;971620

SQL Reporting Services Split Expression

=(Replace(Fields!WebUrl.Value, Parameters!ParentUrl.Value, "")).Split("/")(0)

SharePoint disallowed special characters

http://support.microsoft.com/default.aspx?scid=kb;en-us;905231

SharePoint 2007 SP2 will expire your site in 180 days

Oops, somebody should be fired for this mistake. Apparently after you install SP2, start the count down because in 180 days your site is going to die. All the data will be intact but users won't be able to access it.

http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx

Wait for the hotfix before you install the service pack.

I Love Xobni

I love Xonbi (inbox spelled backwards), I can't tell you how much time this add-in has saved me.

http://www.xobni.com/

April CU Update is available

Install WSS first then MOSS then run the SharePoint Configuration wizard.

WSS - KB968850

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=968850 

MOSS - KB968851

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=968851

Business Contact Manager 2007 Service Pack 2 (BCM 2007 SP2)

In case you haven't heard by now, Office 2007 Service Pack 2 has been released by Microsoft. You can download them from the links in this post by the Office Sustained Engineering Team

One item that isn't included on that page is the link to download Business Contact Manager 2007 Service Pack 2 or BCM 2007 SP2. I strongly suggest you install the Office 2007 SP2 update before updating Business Contact Manager 2007 Service Pack 2 or BCM 2007 SP2. You can find the installation package for Business Contact Manager 2007 Service Pack 2 or BCM 2007 SP2 by going to the following link.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=405aa7e9-e63b-447b-a49b-d4cbd8eea30d

Hopefully it resolves some common BCM problems.

SharePoint Site Themes

Microsoft has released Ten Themes for SharePoint but in order to use them you need to compile them into their solution files. Waste of time.

Ten Themes for SharePoint in VSeWSS Projects

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0a87658f-20b8-4dcc-ad7a-09ad22641f3a

So I did it for you. Here are the ten SharePoint Themes as solution files. SharePoint Themes

You need to deploy them as solutions and then each has a feature that needs to be activated to apply the theme to the site. They are Site Features. Enjoy!

SharePoint February Cumulative Update Available

Install WSS first then MOSS then run the SharePoint Configuration wizard.

WSS - KB961755

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961755&kbln=en-us

MOSS - KB96156

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961756&kbln=en-us

This SharePoint February cumulative update addresses many issues including the Email Enabled Lists problem in my previous post.

SharePoint Email Enabled Lists Unknown Alias

Try installing the hotfix or wait for the February Cumulative Update that includes this hotfix. Once it comes out I'm going to install it and will let everyone know whether the problem reoccurs after the update.

The entries for e-mail-enabled lists are being deleted from the EmailEnabledLists table in the configuration database. When this issue occurs, incoming e-mail messages for these lists are not delivered. Therefore, the e-mail messages are deleted, and errors are logged for "Unkown alias."

http://support.microsoft.com/kb/961750

Programmatically start SharePoint search crawl

Simple code sample on how to programmatically start a SharePoint search crawl through code. I haven't had a use for this yet but it's good to know that search crawls can be started easily.

http://weblogs.asp.net/vikram/archive/2009/02/27/starting-an-incremental-crawl-in-share-point-programmatically.aspx