Not sure why that happened. Here's my original response:
Sorry about the 1 vs 1.1 issue, I should have definitely noticed that.
What you are saying about the MaximumNumberOfResult also makes sense, so thank you for that as well!
Rather than telling you what I think might be happening, I`ll just let you know what I observed and you come to your own conclusion.
I create credentials like this:
var credentials = TwitterCredentials.CreateCredentials(AccessToken, AccessTokenSecret, ConsumerKey, ConsumerSecret);
TwitterCredentials.ExecuteOperationWithCredentials(credentials, () =>
Then I check the rate limit before doing any queries. i use this code:
ITokenRateLimits rateLimits = RateLimit.GetCurrentCredentialsRateLimits();
The result returned is 180, although when I check the Twitter Search API Rate limit it is says I should have 450 for application-only auth. Am I using application-only auth with the credential object I created?
I guess I'm not quite sure how that part works.