There is a vast amount of resources on how you can develop custom components for SharePoint 2010. When it comes to branding, it’s a different story. There are few accepted approaches on how to implement branding in SharePoint and very few guides on how to approach branding tasks as a whole and integrate them into… READ MORE
SharePoint 2010 Branding in Practice A Guide for Web Developers – Ch2 General Overview of SharePoint 2010 Branding; What’s Where and Why?Ebooks
There is a vast amount of resources on how you can develop custom components for SharePoint 2010 like SharePoint 2010 Branding. When it comes to branding, it’s a different story. There are few accepted approaches on how to implement branding in SharePoint and very few guides on how to approach branding tasks as a whole… READ MORE
If you look at a SharePoint application you’ll find that most of its active components are SharePoint 2010 Web Parts. SharePoint 2010 includes dozens of prebuilt Web Parts that you can use. It also provides an API that lets you build custom Web Parts using C# or VB.NET. SharePoint 2010 Web Parts in Action is… READ MORE
Prepare for Artifacts Provisioning in SharePoint 2010 Webinar Summary In this webinar you will learn how to provision artifacts (site columns, content types, list definitions) using the features and feature elements provided by the native SharePoint 2010 extensibility infrastructure. Moreover, you will learn how to use Microsoft Visual Studio 2010 to achieve these goals. Key benefits… READ MORE
Steve Fox, Director of Developer and Platform Evangelism at Microsoft, shares his thoughts on the one thing that people need to know about SharePoint 2010. This is part of ‘The One Thing’ video series produced by Christian Buckley (@buckleyplanet) and the Axceler team.
SharePoint 2010 is coming up to its 2 year birthday, so it worth talking about Ribbons. Too often solutions concentrate on pages, Web Parts, lists, libraries and workflows. A SharePoint solution should be more than this – each of these components should be combined to provide users with a holistic solution, where the components work together and not as discrete entities.
When using a custom Master Page within SharePoint 2010 you may experience the following issue when creating site columns. This error is caused by incorrect syntax within the master page itself. To reproduce this issue, do the following.
SharePoint 2010 Upgrade is not over yet. While some estimates recently put it at 50% I get a different picture from my recent visit to Bulgaria. I had a nearly full theatre room with those interested in SharePoint 2010 upgrade. There are still a number of customers waiting and looking at SharePoint 2010 and trying to decide when they should do it. I have done a number of posts on Why Upgrade to SharePoint 2010 both for IT and Top 10 Reasons Why You Should Upgrade for End Users. Any post on issues in 2010 or browser and ActiveX controls should not discourage you. It’s definitely worth it.
With the release of SQL 2012, Reporting Services got a remake specifically for SharePoint 2010. Reporting Services can now be configured as a service application specifically to allow for scaling within your infrastructure. To enable this in SharePoint you must first have installed the SharePoint component from SQL 2012. You can find this by running the installer for SQL and selecting the following:
In a previous post I shared some thoughts regarding changes to authentication providers in SharePoint 2010. As I worked through the issue of removing Claims/FBA and reverting to NTLM I discovered a number of issues that manifested themselves in strange ways. The first problem I encountered was the inability for a Farm account to make changes to the Authentication Providers settings in Central Administration. The System Account couldn’t even view the dialog – each attempt resulted in a 403 error. This was bad news as a lot of things happen behind the scenes when changing authentication settings in this dialog – not the least of which is propagation of changes to all the web servers. This meant I would have to undo all of the Claims settings manually and repeat them on each server. Not my idea of a fun afternoon.