Thanks for these quick replies. I really appreciate it.
In 0.9.9.0 I have made an important refactoring of the Web Layer with the intention of making each query more customizable.
This is the case of the Timeout property.
As you mentioned each of the ITwitterQuery should be set by default by the
The hardcoded value is intentional. I wanted to make sure that an invalid set up of the Timeout will not make queries to fail.
I will fix the error reporting issue by using the TwitterQuery instead of the ITweetinviSettingsAccessor.
In the meantime I still want to understand how you can get an error with your code.
If you use the Source Code could you check the properties of the TaskCancelledException?
If not, I will need a repro project to be able to reproduce and fix the issue.
Linvi
In 0.9.9.0 I have made an important refactoring of the Web Layer with the intention of making each query more customizable.
This is the case of the Timeout property.
As you mentioned each of the ITwitterQuery should be set by default by the
APPLICATION_WEB_REQUEST_TIMEOUT.The hardcoded value is intentional. I wanted to make sure that an invalid set up of the Timeout will not make queries to fail.
I will fix the error reporting issue by using the TwitterQuery instead of the ITweetinviSettingsAccessor.
In the meantime I still want to understand how you can get an error with your code.
If you use the Source Code could you check the properties of the TaskCancelledException?
If not, I will need a repro project to be able to reproduce and fix the issue.
Linvi