Category Archives: SharePoint

All SharePoint related posts

Easily Allow Content Authors To Open Links as Dialogs


SharePoint 2010 introduces the new Dialog functionality that allows users to easily edit and update items from links on a page without having to leave that page; this works well and has a nice user experience.  The dialog functionality is primarily intended for use when editing list items or document properties, but I have had numerous requests to open other content (like news items) in dialogs as well.  This is relatively simple to do through JavaScript but does require a developer to be involved for each request, which is often time-consuming and expensive.  Ideally, there should be a way for the Content Authors themselves to specify which links open as dialogs and which do not.  Click to read the full post

The SharePoint Content Editor and the Infinite JavaScript Problem


One of the nice things about the SharePoint Content Editor Web Part is that it lets you easily include your own html and javascript without having to modify the page structure itself and that works really well for most things.  However, many third-party and hosted utilities require you to embed a script in your content that looks something like this :

   <script type="text/javascript" charset="utf-8" src="http://external.url.com/SomeID/TheirApp.js"></script>
   <noscript><a href="http://external.url.com/SomeID/">Click here to do something wonderful</a></noscript>

Simple enough and anyone can paste that in.  The catch comes when the javascript file that you are including writes its own HTML into your page. Click to read the full post

Automatically Set the AssemblyFileVersion for Visual Studio Projects


One of the more annoying quirks with dealing with SharePoint is that once you develop a solution that requires custom code, all dependencies are then tied to the Strong Name of the compiled DLL.  That strong name also includes the version number, usually 1.0.0.0, and cannot be changed without breaking all existing references.  This is a good thing from a compatibility perspective but it does make it rather complicated to figure out exactly which version of a DLL is in use.

You can open up the WSP and then use the timestamps and take a guess at the version but it is not always reliable.  Click to read the full post

Phone Numbers in SharePoint and Lync 2010


So, I get an email from a client complaining that their phone icon is not appearing next to some phone numbers in SharePoint but is appearing for others, to which my immediate response was: “What phone icon?”

After some digging, it turns out that this client recently upgraded to Lync 2010 and one of the features in this version of Lync is “Phone Number Detection” that is implemented as an Add on to Internet Explorer. It merely scans the contents of each web page looking for any text that matches a known phone number format.  If phone numbers are found, it then injects html into the already loaded html that will display a small phone icon next to the number. This added html also enables the ability to click on that icon and have Lync dial the number for you.

All in all, a pretty handy feature except if you are editing content in SharePoint.  You see, Lync has no knowledge of “edit mode” of a SharePoint page so it can’t tell that you are editing content in the page and thus doesn’t know to leave the content alone.  Click to read the full post

Explorer View versus the Large Document Library


Recently, I came across the error below when attempting to open a large document library in Explorer View :

Some/SharePoint/Folder is not accessible.  You might not have permission to use this network resource. Contact that administrator of this server to find out if you have access permissions

Folder is not accessible.  You might not have permission to use this network resource. Contact that administrator of this server to find out if you have access permissions

Seeing as I am the administrator of the server, the site collection, the web application and the entire farm itself, I think I pass the permissions test.  It turns out that the real culprit has absolutely nothing to do permissions in any way.

Click to read the full post