Archive for the ‘Sharepoint 2010’ Category

After some years developing projects with Microsoft Sharepoint, a part that many consultants and IT managers leave behind when building Sharepoint solution and web in general, is the way content are organized and the formulas used to build the information architecture of the solution.



Information Architecture can be described as “the science of organizing and labeling websites, intranets, online communities and software to support usability.”

In detail and having Sharepoint as a starting point when we talk about Information Architecture we include:

  • site taxonomy/structure
  • metadata
  • search schema
  • navigation
  • content tree

I Navigation i.e. is automatically driven by the site’s structure, your site taxonomy will impact the usability of your navigation.

As better designed and adapted to the organization is an Information architecture more close you are to achieve the following goals:

  1. Usability – Sites that lack a well-thought out IA tend to be less usable.  It’s more difficult to find information and site navigation tends to be substandard or confusing.
  2. Compliance – Policies that allow us to adhere to compliance regulations are quite often driven by metadata.  If the metadata design is lacking, it may be difficult or impossible to stay in compliance, which can have tremendous legal and financial repercussions.
  3. Site Management/Administration – A strong IA will help prevent site sprawl and may help address storage requirements or goals.

Besides my opinion i would like in this post to share with you some off the resources i pass to my colleagues and trainees:





Last week someone had ask me for some tools and good resources for helping him with his old sharepoint projects that were not yet migrated.

I had send him back the list of resources i8 had been using and some developments where i had collaborate. So here it goes some of the best references for you to use  on your projects. Some of them are also a good choice when used in Sharepoint 2013



SPSite Lokup

Multiple providers Authenticattion

sharepoint search xslt configurations
Taxonomie deploys


development frameworks
developer dashboard

start and stop Sharepoint

Google analytics integration Sharepoint

Newsletter Generator

sharepoitn factory

Tools for kick solutions satartup


I hope this information can be so useful for you, as it had been for me in the last years

The product group released the August 2012 Cumulative Update for the SharePoint 2010 product family.

Be aware that the August Cumulative Update for SharePoint 2010 is a Post-SP1 hotfix. That means that you should ensure that SP1 is installed before the August CU.

” Stefan Goßner


Find out more at

A lot of projects had been implemented by the team where i belong, using Sharepoint 2010 in some of the projects we had found an issue with the outoff the box redirect page.


The first 2 problems we had seen was:

– Absolute URL are saved even when we want to save just the relative url. This is can be a problem when we are in Webapplications that have more then a zone (a typical case in Internet facing projects default zone for editing + internet zone for clients).

– When a new page with redirect page layout is checkin or publish the page it loses the redirect url field value.

Both problems have workarounds and until know the answer to both problems by the support team as been using that workarounds. In the first case the solution passes by using absolute URL’s and to be edit in the extension that will be present to the public clients. In the second case there are two public workarounds:

1. Save it and check in it at your site > pages library .

2. A powershell script that solves at a content database level the problem and that should be run when a new redirection page is created.

After a couple of discussions about this topic in my Sharepoint projects we will use a different approach creating or own PageLayout for redirection cases. This is what i will suggest to every one who is at this time starting a new public internet facing project.

It seems that this old issue was not until now considered a topic to be addressed in a cumulative update so as a protection in the projects you develop is to not use this kind of features with known issues.


Thanks to i had found a useful step by step how to build a costume Membership and Authentication provider for Sharepoint.

This kind of customization is very useful in extranets and website with a restricted area that goes outside the AD boundries. In fact in the past days i had my self to do a concept proof of integration between Sahrepoint 2010 and outsystem for a client my and if i had this information it could be quickly to implement.

So many thanks to the Chanakya Sharing and below you have the links

Part 1,
Part 2

Part 3,
Part 4

Just a quick note:

This implementation is for Moss 2007 but is equal when you pretend to use Forms authentication.If you want to create Forms authentication with Claims then you should find another kind of resource like

Some advices:

If you are creating a forms authentication and have no schema or User’s (directory, bd what ever) source, it may be useful to use the ASP.NET Form’s authentication method you can find how in and for management of the user’s you can use the following artifact or

If you want some code that refer to the FBA Claims to explore you can get two interesting examples in

Do you know what to do when we need to make a deploy specific to the style library or other logical folder of sharepoint 2010?

The solution is pretty simple but for most is not obvious so here goes the simple steps:
1- Create a Feature
2- Copy the resources to your feature folder
3- In the manifesto of your feature instantiate a module and define something similar to

The File element defines the resource to copy.
The url of the element indicates the destiny of the copy
The Path indicates the origin of the copy
Pay attention to what you choose in to the Type becouse here you can define if you intend to make the element ghostable or not.

one off the most important things when building software is to learn from the past, in two ways:
– To be a and produce better
– To have time to create new and improve

The same is valid when working over a platform, In Sharepoint development i see so many times the same mistakes, in this post i will let you to powerful resources that you really should read.

If you accomplish this best practices i am sure that you will improve as developer also your products will improve and the better of all works you will understand better your framework.

So if you are working with Sharepoint 2010 don’t miss this chance to be better.