DirectorySearcher.SizeLimit Property
.NET Framework 3.5
Gets or sets a value indicating the maximum number of objects that the server returns in a search.
Assembly: System.DirectoryServices (in System.DirectoryServices.dll)
| Exception | Condition |
|---|---|
| ArgumentException |
The new value is less than zero. |
Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
Note the differences between Paged and Non-Paged searches
Paged searches will chunk up the result data and return data to the client, whilst the search continues.
Non-paged searches will try to do the entire search on the server, and then return the results.
The SizeLimit property will only affect non-paged searches. Even when the SizeLimit is set to zero the number of results will be limited by the server (usually 1000).
To do a non-paged search leave the PageSize property as the default = 0.
A paged search will return all results, without limit.
To do a paged search set the PageSize property greater than 0, and less than the maximum page limit size (~1000).
Non-paged searches will try to do the entire search on the server, and then return the results.
The SizeLimit property will only affect non-paged searches. Even when the SizeLimit is set to zero the number of results will be limited by the server (usually 1000).
To do a non-paged search leave the PageSize property as the default = 0.
A paged search will return all results, without limit.
To do a paged search set the PageSize property greater than 0, and less than the maximum page limit size (~1000).
Note: