Provider. Find State(PersonalizationScope, PersonalizationStateQuery, Int32, Int32, Int32) Method
When overridden in a derived class, returns a collection containing zero or more PersonalizationStateInfo-derived objects based on scope and specific query parameters.
public: abstract System::Web::UI::WebControls::WebParts::PersonalizationStateInfoCollection ^ FindState(System::Web::UI::WebControls::WebParts::PersonalizationScope scope, System::Web::UI::WebControls::WebParts::PersonalizationStateQuery ^ query, int pageIndex, int pageSize, [Runtime::InteropServices::Out] int % totalRecords);
public abstract System.Web.UI.WebControls.WebParts.PersonalizationStateInfoCollection FindState (System.Web.UI.WebControls.WebParts.PersonalizationScope scope, System.Web.UI.WebControls.WebParts.PersonalizationStateQuery query, int pageIndex, int pageSize, out int totalRecords);
abstract member FindState : System.Web.UI.WebControls.WebParts.PersonalizationScope * System.Web.UI.WebControls.WebParts.PersonalizationStateQuery * int * int * int -> System.Web.UI.WebControls.WebParts.PersonalizationStateInfoCollection
Public MustOverride Function FindState (scope As PersonalizationScope, query As PersonalizationStateQuery, pageIndex As Integer, pageSize As Integer, ByRef totalRecords As Integer) As PersonalizationStateInfoCollection
A PersonalizationScope with the personalization information to be queried. This value cannot be
A PersonalizationStateQuery containing a query. This value can be
The location where the query starts.
The number of records to return.
The total number of records available.
This method is the abstract definition of an administrative method for querying personalization data. Derived implementations should follow the logic described below.
The set of returned items is constrained by the
pageSize parameters, where
pageSize sets the number of records to return and
pageIndex sets which records to return. For example, a
pageIndex of 0 and a
pageSize of 25 would return the first 25 occurrences, while a
pageIndex of 1 and a
pageSize of 25 would return occurrences 26-50. If you want to retrieve all available records, set
pageIndex to 0 and
pageSize to MaxValue.
This method passes query wildcard characters to the underlying data store. Support for wildcard characters is currently dependent on how each provider handles characters such as an asterisk (*), a percent symbol (%), or an underscore (_).
Normally, for SQL-compliant data stores, you can perform a wildcard search on a partial path with the wildcard character appearing at the beginning, the end, or the middle of the search string text in the PathToMatch property. For example, to find all paths that start with "~/vdir", the PathToMatch property would be set to "~/vdir%".
Likewise, a wildcard search on a partial user name could have the wildcard character appear at any point in the text string of the UsernameToMatch property. For example, to find all user names that start with "John", the UsernameToMatch parameter would look like "John%".
The following query constraints apply:
scopeis provided, and
nullor all the properties on
nullor default values, then all records matching the indicated
scopeparameter are returned.
If the UserInactiveSinceDate property is not equal to MaxValue, then the returned records are also filtered to return only those records associated with inactive users. The comparison includes records where the LastActivityDate property is less than or equal to the UserInactiveSinceDate property.
Note that this method does not validate combinations of query parameters. For example, code can request a set of personalization state records associated with a specific user name in the shared scope. Because user names are not associated with shared information, the returned collection would be empty.
Parameter combinations that have the potential to return a non-empty collection include: