[Test]
public void does_not_throw_exception_on_non_existing_file() {
Assert.DoesNotThrow(() = File.SetAttributes(DOESNOTEXIST,
FileAttributes.ReadOnly));
}
Cheers,
Greg
--
Le doute n'est pas une condition agréable, mais la certitude est absurde.
bizarre, their docs say it should throw but they don't.
http://msdn.microsoft.com/en-us/library/system.io.file.setattributes.aspx
Not sure which is better, what they say they do or what they do?
On Fri, Aug 10, 2012 at 10:01 AM, Greg Young gregoryyou...@gmail.com wrote:
[Test]
public void
Historically, mono has done what .Net does rather than what it says.
- Jonathan
On Fri, Aug 10, 2012 at 1:07 PM, Greg Young gregoryyou...@gmail.com wrote:
bizarre, their docs say it should throw but they don't.
http://msdn.microsoft.com/en-us/library/system.io.file.setattributes.aspx
Not
I'm fine by that. Is there a list of these incompatibilities that is
being maintained?
On Fri, Aug 10, 2012 at 8:09 PM, Jonathan Chambers jonc...@gmail.com wrote:
Historically, mono has done what .Net does rather than what it says.
- Jonathan
On Fri, Aug 10, 2012 at 1:07 PM, Greg Young
If you want, you could implement the correct behaviour and then submit
the patch with that unit test attached as a github pull request. We
will easily and quickly be able to merge the new behaviour in then.
Alan
On 10 August 2012 18:10, Greg Young gregoryyou...@gmail.com wrote:
I'm fine by
There is incompatibility between those two implementations. I found it
while implementing my own Server and Client channels' sinks.
Implementation works on .net but not on mono (throws exception that
there was error in tcp connection).
I already filled a bug:
