Recently we have seen how to Delete Web parts in SharePoint 2010 and 2013 with Windows PowerShell. A logical next step would be to add Web Parts also with Windows PowerShell. So we would have two scripts with which we may replace a given Web element by another. An example of use?
See Beyond The Numbers: Data Visualization with Status Lists in Sharepoint 2010 – part 1 Sharepoint List based Status Indicator and Excel based Status Indicator
Sharepoint 2010 is the IWs place of predilection for creating, authoring and sharing insights using a palette of tools like Excel Services, Performance Point Services, Access services, Power View, Visio services, 3rd party visualization tools and so on.
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:
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.