tips & tricks
Working easier with custom CAS policies
Working with custom CAS policies is not trivial. Many developers find it challenging to figure out what permissions their code should have, so instead deploying safely to Web Application (BIN) they choose to deploy their assemblies to the Global Assembly Cache (GAC) granting their code full trust. There is however one trick that makes it very easy to find out what permissions you should grant to your code. Find out how to craft your custom CAS policies the easy way.
Extending all SharePoint Project Item Types – Extending Visual Studio SharePoint Developer Tools tip #10
When extending standard functionality of SharePoint Project Item Types in Visual Studio 2010 SharePoint Developer Tools there are scenarios when you might want your extensions to be available on all types of SharePoint Project Items. Find out how to make your custom functionality available to all SharePoint Project Item Types.
Creating better RSS feeds with SharePoint 2010 Content Query Web Part
Content Query Web Part (CQWP) allows you to easily create RSS feeds for your content. With SharePoint 2010 it became even easier as you can use slots to map your fields to RSS fields. There are however a few things you should keep in mind to get the most out of an RSS feed created using the CQWP. Find out how to create a proper RSS feed with the SharePoint 2010 Content Query Web Part.
Extending the SharePoint 2010 Ribbon Quick Access Toolbar
SharePoint 2010 includes the Ribbon which makes it easier for users to work with the rich functionality of the SharePoint platform. The Ribbon in SharePoint 2010 also includes a rich extensibility framework which makes it possible for custom solutions to make their functionality available to users. Using the Ribbon extensibility framework you can add all kinds of controls to the Ribbon but is it also possible to extend the Quick Access Toolbar?
Building Visual Studio 2010 extensions in one project – Extending Visual Studio SharePoint Developer Tools tip #9
When building extensions for Visual Studio 2010 SharePoint Developer Tools, VSIX project by default does only the packaging. Your extension’s code has to be included in a separate assembly. Did you know however that all you need is a simple trick to build your extension using a single project?