PersonalizationProvider.ResetPersonalizationBlob Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
When overridden in a derived class, deletes raw personalization data from the underlying data store.
protected:
abstract void ResetPersonalizationBlob(System::Web::UI::WebControls::WebParts::WebPartManager ^ webPartManager, System::String ^ path, System::String ^ userName);
protected abstract void ResetPersonalizationBlob (System.Web.UI.WebControls.WebParts.WebPartManager webPartManager, string path, string userName);
abstract member ResetPersonalizationBlob : System.Web.UI.WebControls.WebParts.WebPartManager * string * string -> unit
Protected MustOverride Sub ResetPersonalizationBlob (webPartManager As WebPartManager, path As String, userName As String)
Parameters
- webPartManager
- WebPartManager
The WebPartManager managing the personalization data.
- path
- String
The path for personalization information to be used as the data store key.
- userName
- String
The user name for personalization information to be used as the data store key.
Remarks
Classes that derive from PersonalizationProvider and implement this method should use the webPartManager
, path
, and userName
parameters as storage keys. Derived implementations must modify the data store so that personalization data for supplied storage keys is effectively deleted. It is up to the derived implementations as to how they physically accomplish this.
The derived personalization provider must be able to distinguish personalization data on a per-page basis. Furthermore, for a given page's state, the personalization provider must be able to distinguish between Shared and User scope data. If a non-null
user name is provided, then the reset operation applies to the User scope; otherwise, the reset operation applies to the Shared scope.
Applies to
.NET
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기