Closed yartat closed 7 years ago
Any reason why you removed the async
from the overloads and only the overloads "doing the job" keep the async
keyword?
Thanks for response. I removed async
because it not necessary. "Doing the job" has been already returned result as Task<bool>
.
OK, maybe we should give `WebDavClient
the same async treatment.
But honestly, I don't like the additional parameter on every method of WebDavSession
. Another way of doing this would be to add a property to WebDavSession
to enable/disable the throwing of exceptions.
It have a sense. I'll fix it
Please, check my commit
I've seen that you target net46 and netstandard2.0 Do we use any features of .NET Standard 2.0? Otherwise I'll leave the target to .NET Standard 1.1.
Even when used on a .NET Standard 2.0 project, the .NET Standard 1.1 version of the library will work.
See, I don't see any advantages of targeting .NET Standard 12.0, what do you think?
Thanks for response. All libraries from .NET Std 1.x work fine in .NET Std 2.0, so, targeting to 2.0 should remove :)
Looks fine
OK, merged.
Thanks for the contribution!
Updated NuGet package and online documentation.
Currently WebSession returns
Task<bool>
and caller must check result. I suggest throw exception in case error response from WebDAV. To capability with existing code I added parameterthrowException
with default value isfalse
. So, all existing code will produce with old expected behavior, and new code can choose uses exceptions or checks result.