--- title: "RSReportDesigner Configuration File | Microsoft Docs" ms.date: 03/20/2017 ms.prod: reporting-services ms.prod_service: "reporting-services-native" ms.technology: report-server ms.topic: conceptual helpviewer_keywords: - "Report Designer [Reporting Services], configuration file" - "RSReportDesigner configuration file" ms.assetid: fdcc9c58-3bad-45b3-ba8e-c7816d64f14c author: maggiesMSFT ms.author: maggies --- # RSReportDesigner Configuration File The RSReportDesigner.config file stores settings about the rendering and data processing extensions available to Report Designer. Data processing extension information is stored in the **Data** element. Rendering extension information is stored in the **Render** element. The **Designer** element enumerates the query builders that are used in Report Designer. Report Designer uses embedded report server functionality to preview reports. Server-related settings can be specified to support local server-side processing for preview operations. For more information about report server configuration settings, see [RsReportServer.config Configuration File](../../reporting-services/report-server/rsreportserver-config-configuration-file.md). ## File Location This file is located in the \Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies. ## Editing Guidelines Do not modify the settings in this file unless you are deploying or removing a custom extension, disabling caching during preview, or registering a new data processing extension after a Service Pack upgrade. Specific instructions for editing configuration files are available if you are customizing rendering extension settings. For more information, see [Customize Rendering Extension Parameters in RSReportServer.Config](../../reporting-services/customize-rendering-extension-parameters-in-rsreportserver-config.md). For general instructions on how to edit configuration files, see [Modify a Reporting Services Configuration File (RSreportserver.config)](../../reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config.md). ## Example Configuration File The following example illustrates the format of the RSReportDesigner.config file. ``` . . . . . . . . . ``` ## Configuration Settings |Setting|Description| |-------------|-----------------| |**SecureConnectionLevel**|Specifies the degree of security of the Web service connection. Valid values range from 0 through 3, where 0 is least secure. For more information, see [Using Secure Web Service Methods](../../reporting-services/report-server-web-service/net-framework/using-secure-web-service-methods.md).| |**InstanceName**|An identifier for the preview server. Do not modify this value.| |**SessionCookies**|Specifies whether the report server uses browser cookies to maintain session information. Valid values include **true** and **false**. The default is **true**. If you set this value to false, session data is stored in the **reportservertempdb** database.| |**SessionTimeoutMinutes**|Specifies the period for which a session cookie is valid. The default is 3 minutes.| |**PolicyLevel**|Specifies the security policy configuration file. The valid value is Rspreviewpolicy.config. For more information, see [Using Reporting Services Security Policy Files](../../reporting-services/extensions/secure-development/using-reporting-services-security-policy-files.md).| |**CacheDataForPreview**|When set to **True**, the Report Designer stores data in a cache file on the local computer. Valid values are **True** (default) and **False**. For more information, see [Previewing Reports](../../reporting-services/reports/previewing-reports.md).| |**Render**|Enumerates the rendering extensions that are available to Report Designer for preview purposes. The set of rendering extensions that are used for preview should be identical to those installed with the report server.

**Name** specifies the rendering extension. If you are invoking a rendering extension through code, use this value to call a specific extension.

**Type** specifies the fully qualified class name of the extension class, plus the library name, comma separated.

**Visible** specifies whether the name appears in any user interface. This value can be **True** (default) or **False**. If **True**, it appears in user interfaces.| |**Data**|Enumerates the data processing extensions that are available to Report Designer for the purpose of connecting to data sources that provide data to reports. The set of data processing extensions used in Report Designer may be identical to those installed with the report server. If you are adding or removing custom extensions, see [Deploying a Data Processing Extension](../../reporting-services/extensions/data-processing/deploying-a-data-processing-extension.md).

**Name** specifies the data processing extension.

**Type** specifies the fully qualified class name of the extension class, plus the library name, comma separated.| |**Designer**|Enumerates the query builders that are available to Report Designer. Query builders provide a user interface for constructing queries that retrieve data used in reports. Query builders may vary for different data processing extensions. By default, Reporting Services provides one visual data tool user interface for all data processing extensions that are included in the product. However, if you are building or using third-party data processing extensions, other query builder interfaces may apply.| |**PreviewProcessingServiceStartupTimeoutSeconds**|Specifies the period to wait for the preview processing service to start up before showing an error message. The default is 15 seconds.| ## See Also [Reporting Services Configuration Files](../../reporting-services/report-server/reporting-services-configuration-files.md) [Query Design Tools (SSRS)](../../reporting-services/report-data/query-design-tools-ssrs.md)