Mandating of contentMD5 argument inconsistent about azure-storage-net HOT 1 CLOSED

Thanks for reporting this, you are right there is an inconsistency that we will fix in an upcoming release. Because there are so many combinations of parameters / headers for each api the client lib provides one "min" overload that acceptes only the required parameters, and then one "max" overload that accepts all possible parameters, and each can accept null as a valid input. This allows users to utilize the features they require without requiring large number of overloads for each api in the library.

We are going to also update the intellisense documentation for the contentmd5 parameter as it is currently misleading. The correct usage of this parameter is to set the Content-MD5 header on the request in order to provide transactional integrity. If the parameter is null and the client / requestOptions are configured to require TransactionalIntegrity then the data will be read in order to calculate this value internally. As such providing the md5 value if it is known is a performance feature allowing clients to skip this duplicate read of the data prior to sending the request.

from azure-storage-net.