I suggest removing the dependency on autofac as that should be a design consideration ultimately left up to the project using a library, not the library itself.
Comments: ** Comment from web user: linvi **
Hi there,
Thanks you for the feedback but could you elaborate a little more.
__I was unable to use this project because it has fairly complex dependencies that make assumptions about the system it's running on.__
Could you please describe WHY would a dependency on Autofac result in you being unable to use the project?
What do you mean by "make assumptions on the system? Tweetinvi is compatible with Windows Phone, Windows 8, Mono... and __there is not even one condition based__ on a system it is running on (as opposed to many other libraries).
__I suggest removing the dependency on autofac as that should be a design consideration ultimately left up to the project using a library, not the library itself.__
I could do that but I think that 99% of the developers will be unhappy. I don't consider dependency injection is not an easy subject that all developers can implement correctly.
Tweetinvi is already abstracting the dependency injection, and you could if you want use another dependency injection library by simply implementing the interface ITweetinviContainer.
I could maybe provide a way to extend this container and set it but at the current time you will simply need to change the Source Code if you want to do that.
Please give me more details as I am quite happy to discuss the subject.
Linvi