By Trent L. Taylor - 8/13/2012
There have been some minor optimization improvements in this build as well as a few minor bugs. One of the more pressing bugs resolved in this build pertains to the TripleDESWrapper and the CryptoStream class. As part of previous builds, we had made an optimization improvement to ensure that all streams were disposed. However, there turns out to be an inconsistency in the .NET behavior of the CryptoStream class. When a Dispose is called on the CryptoStream, it also closes the underlying base stream that the CryptoStream just wrote to. This in turn, caused a disposed or inaccessible stream error.
Here is the code in the .NET CryptoStream class that caused the error:
|
|