I had the pleasure of presenting at not one, but two (!!) user groups in Australia this past week to discuss the pitfalls of migrating to SharePoint 2013 and all the things that go wrong along the way.
First up, the Sydney SharePoint User Group located in the heart of the CBD. Sydney is my home away from home for the next few years, and I’m very grateful to the organisers for giving me the opportunity to come out.
The following day, after a quick train ride and some kangaroo sightings, it was off to Canberra for the Canberra SharePoint User Group. There were some projector issues, but I do hope that everyone that attended got something out of the session.
Today marks the official release of SharePoint Designer as a free product offering from Microsoft. While overall, this announcement can certainly be considered a good thing by the SharePoint community (who doesn’t like free stuff?), as a SharePoint “administrator” it makes me cringe. It is a good thing all of us have “locked down" SharePoint Designer in our respective environments.
You did remember to lock down, didn’t you?
MSDN Magazine has a SharePoint focused article this month titled 10 Best Practices For Building SharePoint Solutions. If you’re trying to wrap your head around the scope and depth of developing solutions on top of SharePoint, the article makes for a good primer.
When developing custom InfoPath initiation forms for my workflows, I sometimes forget a crucial step when publishing the forms. If you enter an alternate location when publishing your form, the form state will become stuck on “Installing”.
The moral of the story? When publishing a custom initiation form, be sure to leave the “Alternate” publishing location empty.
SPTraceView (by Hristo Pavlov) is a tool which allows a user (with console and/or RDP access to a SharePoint server) to view the trace logs for SharePoint in real time. Parsing through ULS logs can be a tedious process, but being able to see the events as they occur certainly makes it much more palatable.
SPTraceView can be used in either a single server or a farm scenario, although a farm does require some configuration.
Maxime Bombardier has a post on the subject of fixing one of the bigger issues with the Content Editor web part. For the uninitiated, a Content Editor web part always renders absolute URLs when the rich-text editing capabilities are used. I must admit that I would have never have thought to use a control adapter to manipulate the output of the web part on the fly. Now that I have learned something new, you should too.