CHAPTER 7 USING CUSTOM .NET CODE WITH REPORTSListing 7-5. Named Permission Sets for Reading Files
<PermissionSet
class="NamedPermissionSet"
version="1"
Name="EmployeePayFilePermissionSet"
Description="Permission set that grants read access to my employee cost file.">
<IPermission
class="FileIOPermission"
version="1"
Read="C:\Temp\EmployeePay.xml" />
<IPermission
class="FileIOPermission"
version="1"
Read="C:\Temp\EmployeePay.xsd" />
<IPermission
class="SecurityPermission"
version="1"
Flags="Execution, Assertion" />
Next, as shown in Listing 7-6, you add a code group that grants the assembly the additional
permissions to the CodeGroup section of the policy configuration file rssrvpolicy.config. If you have
already added the FullTrust permission to the assembly, you can replace it with this CodeGroup instead,
or simply modify it to use the newly created permission set name.
Listing 7-6. 'ranting File IO Permission on the EmploYee AssemblY
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName=" EmployeePayFilePermissionSet "
Name="EmployeePayCodeGroup"
Description="Employee Cost Per Visit">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting
Services\ReportServer\binEmployee.dll "/>
Note The name of the assembly that you add to the configuration file must match the name that is added to the
RDL under the CodeModules element. This is the name you set for the custom assembly under the Report
Properties References menu, which was introduced in the “Accessing .NET Assemblies from Embedded Code”
section; it is discussed in detail in the “Adding an Assembly Reference to a Report” section.