On SolidQ blogs we have talked sometimes about working with XSLT in Sharepoint 2010, manipulating XML structures and the combination of both technologies to generate HTML. It is very important to learn how to work with these tools in Sharepoint 2010, since many Web Parts by default allow the personalization combining these technologies. This is the case of Content Query Web Part, Data Form Web Part and so on, that as we know, they are suitable for some tasks but not such as good for another ones. Could it be possible to generate a Web Part to carry out a very specific task that we need, and make it capable of personalizing at our discretion using XSLT? The answer is yes, so let’s see how. Firstly, we are going to observe the list of ingredients:
I’ve been customizing some XSLT from the ItemStyle.xsl file for the SolidQ Summit SharePoint site. Well, to be fair my colleague José Quinto (@jquintozamora) did it the last year, and I’m applying some modifications requested for this year’s event.
Here we go again with a short (but very useful) post. As part as the good performance practices when we are coding we have to avoid exceptions, there is a usual exception in our SharePoint code, the redirect exception.
This week I have been working on the creation of a custom control of ASP.NET, its main function is to generate the popular “social buttons” of some social networks (Facebook, Twitter and LinkedIn until now), which allows sharing amongst those links in social networks to any article, web, etc.
In SharePoint we have five OOB roles or permissions levels: Limited Access, Read, Contribute, Design and Full Control. If we want to check if current user have one permission level or higher, we can use this function: