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.
Recently I’ve been working on a SharePoint solution that was persisting some state information. Originally this solution was relying on Session State but because of some extra configuration complexity that using Session State with SharePoint requires we decided to replace the Session State with cookies. Although both approaches are not exactly the same they were both sufficient in the scope of the solution. And although you might expect no rocket science when working with ASP.NET cookies there are a few things that keeping in mind might save you some painful hours.
For the last couple of weeks I spent some extra time on learning. I have decided to organize my knowledge and experience and fill in all the gaps.
Control Adapters are a great way to modify the presentation layer of any control out there: no matter whether it’s sealed or internal. And while they are pretty easy to setup you can find yourself spending a couple of hours if somehow they seem not to be applied…
While developing custom SharePoint solutions there is a big chance you need to look into the SharePoint SDK on regular. To keep off continuously surfing to the on-line reference, the SharePoint Team have provided us with the compiled CHM files. I admit that the off-line help files do simplify finding the information on a particular class, method or property. They have however two serious flaws: the content is outdated and there is no community content included in the off-line SDK.