Recent Posts RSS Feed
featured November 1st, 2011

Opening a Modal Dialog on Page Load from Server-Side Code? Don’t Forget This Sweet (and Totally Critical) Function Call

Did you know? Before our page can call upon a modal dialog framework to, say, create a modal dialog, our page has to have *loaded* said modal dialog framework.

Pray tell, then, O scriptacious gods of portal app pop-upage: how can we ensure that the execution of our dialog invocation is delayed until this fine framework is loaded and ready?

Posted: Jon Comments: 0
Action2 September 6th, 2011

Building Configurable SharePoint Solutions

John Ferringer recently spoke at the Fort Wayne SPUG meeting discussing topics in best practices for SharePoint development. During the course of his presentation, one topic was mentioned that struck a chord with me: "be nice to your SharePoint administrators". Some of us in the SharePoint space (in fact, many of my associates) are IT [...]

Posted: Grant Comments: 0
EnableNetBiosDomainNames_thumb.jpg July 14th, 2011

Change User Profile Synchronization Connection without Losing Profile Data

Recently we were dealing with an issue where users were imported from Active Directory into SharePoint User Profiles using the first part of the Fully Qualified Domain Name instead of the NetBIOS Domain Name. This creates issues with the User Profiles, specifically with the Organizational Browser. It appears there is a simple fix by setting the…

Posted: Keith Comments: 0
Passing Data To and From SharePoint Modal Dialogs June 13th, 2011Posted: EricComments: 5

SharePoint Modal Dialogs SharePoint 2010 introduced the ECMAScript Client Object Model. One of the things that it included was the Dialog Framework. This allows modal dialogs to be easily displayed inside of SharePoint. This is typically done by specifying a web page to be displayed as the dialog on top of the current web page. [...]

How To Get IE6-Friendly SharePoint 2007 Development Done on Windows Server 2008 R2 June 1st, 2011Posted: JonComments: 0

The tooling advances that 2010 has provided make it easy to forget that we used to need a Server version of Windows to have a SharePoint instance to develop against, and that, often, the contemporary browser of SharePoint 2007, Internet Explorer 6, was the main target for your work.

And as soon as you get up out of that ridiculous fetal position…

Working with files in SharePoint from ECMA Script May 9th, 2011Posted: GrantComments: 0

Document libraries in SharePoint are quite possibly the most common type of content on a SharePoint site. Working with documents is one of the most critical activities in any enterprise content management endeavor. With that being said, if you’re developing solutions for SharePoint; there WILL come a time when you’ll need to work with documents [...]

Usage and Health Data Service Application Stopped; and a little bit-o-PowerShell April 8th, 2011Posted: GrantComments: 0

If you’ve had the opportunity to work with any of the new Microsoft server products, you’ve undoubtedly become aware of the power of the PowerShell commandlets that ship with many of the new products. As a developer at heart, and a SharePoint developer/administrator by trade; I am enlightened daily by the many things that are [...]

QuickTip: Audience Targeting and List View Web Parts March 11th, 2011Posted: GrantComments: 4

When piecing together a nice little composite application using SharePoint 2010, you will run into circumstances where you will want to hide certain pieces of the UI (Web Parts). As ASP.NET developers we would simply wrap the specified area in a LoginView control and secure it to display for only the appropriate groups. SharePoint Web [...]

Getting a "Trying to use an SPWeb object that has been closed or disposed" Exception? It’s this line in your custom application.master page March 1st, 2011Posted: JonComments: 0

So there I was, minding my own and pooting forth the little green rosettas on a branding solution for a publishing site, when I encountered the following White Screen of Death error:

“Trying to use an SPWeb object that has been closed or disposed and is no longer valid.”

Take the following line out of your version of application.master, and our mystery error will take its ball and go home…