Wednesday, 7 October 2009
Visual Studio 2010 and TFS connection: "The ServicePointManager does not support proxies with the https scheme."
Tuesday, 6 October 2009
SharePoint Tabs Made Easy
While browsing EndUserSharePoint found a good post about using a JQuery script embedded into a CEWP.
From my brief look this basically turned every web part on the page into tabs so that you can create VERY quick and easy tabbed dashboard interfaces. Extremely quick, extremely easy ... the best bit is no code, no development.
You can check out the article (and the video) here: http://www.endusersharepoint.com/2009/10/05/yes-believe-it-the-sharepoint-easy-tabs-interface-web-part/
The History of SharePoint
As we are just two weeks away from disclosing SharePoint 2010 at the SharePoint Conference starting October 19th, I wanted to write three posts to provide context on the upcoming release. This first post will cover the history of SharePoint. I hope it will provide some useful perspective behind our vision and what we have learned as well as a few fun anecdotes. The second post will cover the engineering process for SharePoint 2010 - how we design and develop SharePoint in the Office team, what new approaches we have taken during the 2010 development cycle and my take on a few frequent questions I hear from customers and partners. The third post will coincide with the opening of SharePoint Conference and cover the major feature investments. After that, our team will star blogging in depth about the new SharePoint capabilities. For folks who cannot wait, we have highlighted a few of the new features on the SharePoint 2010 Preview Site as commented on several Office 2010 client capabilities including a few points of SharePoint integration on the Office Engineering Blog.
Before we jump in to this post, I want to thank everyone who has been with us on the journey so far and is supporting us in the release of SharePoint 2010 and feedback for releases beyond. While I will talk about the efforts that evolved into SharePoint, its origin dates to around March 1998 when we first started planning the projects that led to SharePoint. Since the first beta of the first release, we have been extremely fortunate to have your support and hear your feedback. It has been extremely rewarding to see all things you are doing with SharePoint. We have posters of many of your sites on the walls of Building 16 on the Microsoft Redmond Campus and these are a source of great motivation and pride for our team to take things to the next level. We always appreciated your ideas and feedback friendly or otherwise about where the product should go or how we could help you better. We think SharePoint 2010 will be another big step forward but we know there is more to be done and are thankful you care enough to keep pushing us. Finally, we want to thank the Microsoft teams around the world who has worked so hard to build and support the product with special thanks to a few dozen people who were with us from the very beginning in 1998. We are very fortunate to have a great team, customers and partners and that is what keeps us fired up to come to work every day.
Thursday, 1 October 2009
SAS (SharePoint Accessibility Solution) - WCAG 2.0 AAA reusable framework for SharePoint
"Accessibility is mandatory for many organisations, allowing access to the web for all. Our SharePoint 2007 Accessibility Framework allows sites to be built rapidly without sacrificing SharePoint functionality."
- Tim Wallis, CEO, Content and Code
By all means check it out and tell me what you think :)
http://www.contentandcode.com/solutions/Pages/accessibility.aspx
Wednesday, 30 September 2009
Performance Optimisation in SharePoint
Tuesday, 22 September 2009
SharePoint Conference 2009
Wednesday, 16 September 2009
RNIB - World's first AAA website launched in SharePoint
- Full WCAG 2.0 AAA XHTML rendering
- Accessible feature-set
- WYSIWYG Page editing and publishing
- Full list item editing
- Accessible Web Part editing {Add | Remove | Update properties}
- Full list views and list editing (including document libraries, Check-in Check-out and content approval)
- Site Administration (Permissions | Navigation | Basic site settings | features | Recycle Bin | View Site Content}
Friday, 28 August 2009
SharePoint 2010 - Hints, Tips and New Features - Watch this Space!
- Development - Code examples and Walkthroughs
- New Features - new functionality and areas of the SharePoint 2010 product
- Hints and Tips - tricks and "didn't know that .." information about the new build, and my experience with it once it becomes available.
Monday, 17 August 2009
SharePoint Timer Jobs and Multiple Servers
Timer jobs are wonderfully robust creatures. They effectively replace the "Windows Scheduled Task" for SharePoint servers, allowing you to run .Net code on a scheduled or "one off" basis.
However, there can be some confusion about running Timer Jobs on multiple servers, so this should clear it up a bit.
- By default Timer Jobs will only execute on the server that they are called from (typically the Central Administration server)
- Through code you can specify a specific box (SPServer) to run your Timer Job on.
-
It is possible to run a Timer Job on every server on the farm (although this can be dangerous!)
The crux of all this is based on the SPJobDefinition constructor (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spjobdefinition.spjobdefinition.aspx).
The constructor includes a parameter for an SPServer object, which allows you to specify which server the timer job will run on.
Example Code 1 – Add Job to single Server:
The code below is for a Web Application scoped which will register a job definition on a single server. As Web Application scoped features are activated from Central Administration, it will use the current SPServer (i.e. the Central Admin server).
This is useful for code which modified content in the database, as you only want it to execute a single time.
public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWebApplication webApp = properties.Feature.Parent as SPWebApplication;
SPJobDefinition job = new SPJobDefinition("CustomJobDef", webApp);
}
Example Code 2 – Add Job to All Servers:
The code below is for a Web Application scoped which will register a job definition on all web front end servers in the farm.
This is useful for code which modifies files or server settings, as you need it to execute separately for each server.
public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWebApplication webApp = properties.Feature.Parent as SPWebApplication;
foreach (SPServer server in SPFarm.Local.Servers)
{
if (server.Role == SPServerRole.WebFrontEnd)
{
SPJobDefinition job = new SPJobDefinition("CustomJobDef", webApp, server, SPJobLockType.None);
}
}
}
Hope this helps! Enjoy!
Tuesday, 4 August 2009
Turning off Audience Targeting on Page Libraries - Operation is not valid due to the current state of the object
public static void SetTargeting(SPList list, bool enabled)
{
if (list == null)
throw new SPException("List was not found.");
SPField targetingField = GetTargetingField(list);
if (enabled && (targetingField == null))
{
string createFieldAsXml = CreateFieldAsXml();
list.Fields.AddFieldAsXml(createFieldAsXml);
list.Update();
}
else if (!enabled && (targetingField != null))
{
// make sure the field can be deleted!
targetingField.AllowDeletion = true;
targetingField.Sealed = false;
targetingField.Update();list.Fields.Delete(targetingField.InternalName);
list.Update();
}
}