CAS and 3rd Party / Internal SolutionsWhen installing a SharePoint Solution or Web Part you have the choice of Global Assembly Cache (GAC) or BIN installation. When installed into the GAC the assembly (web part) is given 'Full Trust' and the software runs with unrestricted access. If installed to the Bin directory the operations that an assembly can perform are strictly limited using Code Access Security (CAS) configuration. This is called 'Partial Trust'. A security feature of the .NET framework stops an assembly that is given Partial Trust (the caller) using another assembly that has Full Trust (the callee) unless the called assembly has been marked with the AllowPartiallyTrustedCallers attribute. In effect the assembly is declaring that "Its ok for other programs to use me, I will make sure they can't do anything bad". On WSSv3 or MOSS 2007 PivotPoint Web Part follows Microsoft's recommended best practices and installs the web part to the Bin directory and sets the appropriate minimum CAS settings during installation as this method of deployment is much more secure. However, many 3rd party and internally developed solutions don't use Bin/CAS installation and instead deploy to the GAC with full trust and without the AllowPartiallyTrustedCallers attribute What this means is that PivotPoint Web Part will not be able to use any Lists or Fields created using such solution installed into the GAC and these Lists and Fields will not appear in the Configuration toolpart's drop down lists. To solve this you need to either
GAC Installation
|