BADF00D

I tried an older version, but before I wrote this issue, I looked up the current implementation: ```csharp /// /// Specifies the endianness (value byte order) for a field. ///...

We read data send from medical devices via RS232/USB/LAN. Usually the manufacturers of the device defines the endianess once per protocol. In rare cases this is switching during protocol extensions....

Your approach would work, but ``SomeClass`` would not be self describing any more. With the current implementation, we prefer declaring declare the attribute at the field. What do you mean...

Thanks for thinking about it. Btw: Great work!

I tried to reproduce the error in your tests and it seems the bug is a little more complicated the I initially thought. The problem is not within the lazy...

I think this situation (not closed entry stream) can sometimes be detected. I think ``TarHeader.Read`` can check if the reader.BaseStream is aligned to 512 bytes. Or is there a situation...

Maybe I can provide an example. I've encountered a situation where I (with my limited knowledge of NSubstitude) can't find a solution using the current Api. The suggestion would prove...

I had several problems with the version before: I often created events and the "create event popup" was not closed correctly, or the popup was positioned incorrectly. I update to...

I don't use the overview very often, but it looks quite the same.

I had the same problem in 1.0.3 (latest downloadable at owncloud). The latest version here (1.0.4) solved this for me.