Forum Discussion
All of the *V2 interfaces were created due to underlying changes in the way objects are defined. We strive to maintain backward/forward compatibility but there are some situations where the product changes and the API just doesn't work the same way.
Our deprecation policy is to allow for "at least" one year after a method has been deprecated that it still be supported in the product. In most cases, we have to do a bunch of hoops and assumptions under the seems to tie the old versions to the new underlying implementation. As far as I know, aside from when we did a full flush of our APIs to v9, the deprecated methods are still in there. That's not to say they won't go away, but that they might. We recommend you migrate to the new interfaces when you can and when it makes sense.
Sorry for your frustration but we do do our best to make it so you can use a common API across all our software versions - which isn't an easy task.
BTW, I just pushed out the iControl 11.3 API references along with the .Net and Java libs to the iControl Assembly labs project!
-Joe