Bug in C# MultipartShapeBuffer.CalculateExtent() ?

[DanielWalton]

I am seeing some strange behavior in MultipartShapeBuffer.Extent. It seems to be mixing up xMax with yMin. The attached screen capture demonstrates this:

[LanceShipman]

I was able to reproduce your issue. It works correctly with the C++ API, but not with the .NET wrapper. The C++ API returns the extent in xMin, yMin, xMax, yMax order. For some reason the .NET wrapper is returning the extent in xMin, xMax, yMin, yMax order. I've entered a bug.

[DanielWalton]

If it helps, the same issue happens in the Envelope constructor.