Specifies whether all, some, or none of a WebPart control's properties can be exported.
Assembly: System.Web (in System.Web.dll)
All of a Web Parts control's properties can be exported.
None of a Web Parts control's properties can be exported.
Only properties of a Web Parts control that have been defined as non-sensitive can be exported.
A value from the ExportMode property to specify which properties from a Web Parts control can be exported. By default, the properties of a WebPart control cannot be exported and the control's ExportMode property is set to . To enable exporting all properties for the control, set the ExportMode value to . To export only certain properties while preventing the export of properties that contain sensitive data, you set the property value to .enumerator can be applied to the
A property can be marked as sensitive through the PersonalizableAttribute attribute.
To enable the export feature for a Web application that includes Web Parts controls, in the Web.config file for your application, you must add an attribute to the <webParts> element within the <system.web> section, as in the following markup.
The following code example demonstrates the use of the ExportMode property. Note that for the export code example to work, you must also update your Web.config file as indicated in the Remarks section.
The first part of this example contains the code for a control named TextDisplayWebPart. This control is the same as the custom control that is found in the Example section of the WebPart class overview, except that it adds a Personalizable attribute to the TextDisplayWebPart.ContentText property so the property can be exported. Note that the attribute declaration includes a value of true for the isSensitive parameter, meaning that the property is marked as sensitive data for export purposes. For the code example to run, you must compile this source code. You can compile it explicitly and put the resulting assembly in your Web site's Bin folder or the global assembly cache. Alternatively, you can put the source code in your site's App_Code folder, where it will be dynamically compiled at run time. This code example assumes that you compile the source code into an assembly, place it in a Bin subfolder of your Web application, and reference the assembly with a Register directive in your Web page. For a walkthrough that demonstrates both methods of compiling, see Walkthrough: Developing and Using a Custom Web Server Control.
The second part of the example shows how to reference the TextDisplayWebPart control in an ASP.NET Web page. Note that in the declarative markup, the ExportMode property value is set to , meaning that even properties with sensitive values will be exported.
Load the Web page in a browser, and on the verbs menu of the WebPart control, click the export verb and follow the instructions to export a description file containing the control's state and property data.
Available since 2.0