Thanks a lot @stigvoss. I see you even took care to use the same non-standard formatting currently being used in those files. That's a really great work.

Just to give some explanation on why those classes may look so different from the rest of the framework, it's because the MJPEGStream came from the AForge.NET project and they have been barely touched ever since. However, one day it would be nice to be able to go through those classes and update them with the same standards used in the rest of the framework (maybe a relevant issue to track this would be #95).

Again, thanks a lot for the contribution,
Cesar

No problem, I am happy to help. I am aware of Accord's roots in AForge as I used AForge earlier and even though I tried, I failed to stay with the current in-file code convention. :-) Do you have a file or document containing the preferred Accord.NET code convention? If so, I may refactor parts of the Accord.Video library at some point to follow the correct code conventions and possibly increase the testability, and readability of the code.

I do not have a document right now, but they are mostly Visual Studio's default conventions. Whatever Ctrl+E, Ctrl+D gives you should be the standard used across the framework, as this is what most people are likely to be used to.

Oh, one thing I just noticed: After the change, the project does not compile anymore when targeting .NET 3.5. I will try to commit a change in the next few minutes to make the .NET 3.5 version compile again.

Yes, of course. Tasks, as used, was not introduced in .NET Framework till version 4.0 and therefore it makes completely sense. Thank you for correcting the issue.