Allow multiple Dispose calls OR expose Disposed state about microsoft.io.recyclablememorystream HOT 7 CLOSED

Hi @EnCey,

This issue is already fixed in #9

But unfortunately, NuGet package was not updated.
Seems like you have to reuse the latest code version from GitHub in your project

from microsoft.io.recyclablememorystream.

Oh man, didn't check the closed issues. Sorry!
Thanks for the heads up @dr4

from microsoft.io.recyclablememorystream.

We'll be releasing a NuGet update as soon as I can get a handle on getting the binaries properly signed (it is sadly pretty non-trivial)

Date: Tue, 28 Apr 2015 08:32:17 -0700
From: [email protected]
To: [email protected]
Subject: Re: [Microsoft.IO.RecyclableMemoryStream] Allow multiple Dispose calls OR expose Disposed state (#15)

Oh man, didn't check the closed issues. Sorry!

Thanks for the heads up @dr4

—
Reply to this email directly or view it on GitHub.

from microsoft.io.recyclablememorystream.

@doubleyewdee any updates on when the NuGet update will come?

from microsoft.io.recyclablememorystream.

Hey sorry! Working on the code sign stuff. Will try and wrap it this week with a 1.0.1 rev

Date: Tue, 12 May 2015 01:30:02 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [Microsoft.IO.RecyclableMemoryStream] Allow multiple Dispose calls OR expose Disposed state (#15)

@doubleyewdee any updates on when the NuGet update will come?

—
Reply to this email directly or view it on GitHub.

from microsoft.io.recyclablememorystream.

+1 just got bitten by this. Particularly when someone else's StreamReader closes it on my behalf.

from microsoft.io.recyclablememorystream.

Well, it took a while but it works now ;)
Thanks for the update!

from microsoft.io.recyclablememorystream.