If you are serving dynamic binary content via your ASP.net web application with rudimentary code (eg. simple HttpContext.BinaryWrite) you may find that when utilizing audio or video Chrome does not allow fast forwarding/seeking ahead. This is because Chrome relies strictly on the ability to request byte ranges to supply this functionality. This is done with the Accept-Range HTTP response header.
Read More
Arthur
Pemberton
Full-stack web applications developer
Welcome to my blog
As I discover new things in my field and solve troublesome problems, I will attempt to document my finds here.
Error: located assembly’s manifest definition does not match
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Read More