Skip to content

Commit 2546332

Browse files
Update docs/reporting-services/custom-assemblies/deploying-a-custom-assembly.md
Co-authored-by: Maggie Sparkman <maggies@microsoft.com>
1 parent b06b7df commit 2546332

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/reporting-services/custom-assemblies/deploying-a-custom-assembly.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ms.author: maggies
2323
> [!NOTE]
2424
> There are two preview modes for Report Designer: the Preview tab and the pop-up preview window that is launched when your report project is started in **DebugLocal** mode. The Preview tab executes all report expressions using the **FullTrust** permission set and does not apply security policy settings. The pop-up preview window is meant to simulate the report server functionality and therefore has a policy configuration file that you or an administrator must modify to use custom assemblies in Report Designer. This pop-up preview also locks the custom assembly. Therefore, you need to close the preview window in order to modify or update your custom assembly code.
2525
26-
### To deploy a custom assembly in Reporting Services
26+
## To deploy a custom assembly in Reporting Services
2727

2828
1. Copy your custom assembly from your build location to the report server bin folder or the Report Designer folder.
2929

0 commit comments

Comments
 (0)