Vegard's Code Corner

SharePoint 2010 writing to the ULS log

noreply@blogger.com (Vegard Strømsøy) — Fri, 03 Jun 2011 16:02:00 +0000

With SharePoint 2007 there was no out of the box method to write to the ULS log, 2010 however finally remedies this weakness.
Read more »

Reflector alternatives

noreply@blogger.com (Vegard Strømsøy) — Thu, 26 May 2011 18:09:00 +0000

Enough has been said about the RedGate Reflector charging debacle, so I'll leave that alone. If you are looking for alternative software to decompile .NET code here are three to consider.
Read more »

SharePoint 2007 to 2010 upgrade workflow task content type id issue

noreply@blogger.com (Vegard Strømsøy) — Wed, 25 May 2011 18:05:00 +0000

When upgrading from SharePoint 2007 to 2010 I came across a rather odd issue. A custom workflow was no longer using the custom WrkTaskIP.aspx page to host the InfoPath forms as it did in 2007. On closer inspection this was caused by the tasks created from the workflow not having the right content type (and the custom WrkTaskIP page was referenced in the workflow task content type xml file).
Read more »

jQuery to override SharePoint OOTB Upload.aspx default for "Add as a new version to existing files" checkbox

noreply@blogger.com (Vegard Strømsøy) — Tue, 10 May 2011 18:00:00 +0000

A common query from SharePoint users with versioning enabled on document libraries is to default the "Add as a new version to existing files" checkbox on the OOTB upload.aspx page to unchecked. If you google how to uncheck it by default you'll get lots of entries showing you how to simply edit the Upload.aspx file in the \TEMPLATE\LAYOUTS\ folder in the 12/14 hive. This works fine of course if you don't care about tomorrow and having a supported/upgradeable SharePoint installation.
Read more »

PowerShell script to create batch release files for SharePoint wsp files

noreply@blogger.com (Vegard Strømsøy) — Sun, 08 May 2011 20:03:00 +0000

If you have a heavily customised SharePoint installation that is under continuous development here is a quick way to use PowerShell to generate batch files you can hand over to your deployment team alongside the wsp files. If your process consist of managed releases to multiple environments this might be a time saver. As with anything there are many ways to skin a cat, and this is just one example of how to script this repetitive task into a simple drag, drop and click.

Read more »

SharePoint 2007 performance issue caused by too many event receivers

noreply@blogger.com (Vegard Strømsøy) — Tue, 03 May 2011 19:15:00 +0000

If you have a huge number of webs in a SharePoint 2007 site collection with a large number of content types you might have come across some of the more esoteric performance limitations of SharePoint. Regardless of whether you've followed the best practice guidelines for number of sites, lists, list items etc you could fall foul of some rather dodgy SQL in the SharePoint content database.
Read more »

WSPBuilder per project configuration

noreply@blogger.com (Vegard Strømsøy) — Wed, 20 Apr 2011 18:05:00 +0000

When upgrading a custom SharePoint workflow recently I came across a useful feature of WSPBuilder, per project configuration.
WSPBuilder has its own config file WSPBuilder.exe.config which can be overridden in a visual studio project to provide custom settings for that specific project. All you have to do is add a copy of the file to your project from the installed location of WSPBuilder and uncomment any setting you want to override.
Read more »

Team Foundation Server 2010 - Update content of a file being checked in

noreply@blogger.com (Vegard Strømsøy) — Tue, 12 Apr 2011 22:15:00 +0000

Having found the developer blogosphere increasing useful as a source of information for my daily tribulations as a developer, I've decided it's time to contribute something back to the community. Hopefully someone else can stumble upon a useful nugget here that would help them on their way to solving some problem the same way googling has led me to the blogs of countless other developers sharing their bits and pieces.

Recently a requirement came up to insert/update a version number in .sql files on check-in for some Team Projects. When a clients DBA's are looking at stored procs in dev/test/live environments they've got no easy way of correlating the installed version in SQL to a version in TFS besides comparing the actual contents of the stored proc itself. An existing version comment section required manual updates by any developer making a change, mildly error prone as you can imagine. Any sort of automatic version number in the .sql file would ensure the ability to track back to TFS changesets and work items. This should be available as a TFS Check-in Policy so that it could be enabled/disabled for individual Team Projects.
Read more »