With DNN 5 there are so many changes being put in place it's almost impossible to give due warning without writing an essay...

And I'm sure this sort of thing isn't planned months in advance... the decision is just made and it is implimented so that other functionality cannot be delayed. It would be a nightmare to track otherwise. You need to review each version of DNN5 as it comes, and don't tell your customers you support a particular DNN version until you have done the testing - esp with DNN5.

If this method should not have been removed I'm not sure it was well considered... but maybe the functionality broke and it was decided just to withdraw it rather than spend time fixing.

However I know the upmost is being done to make sure things are backwards compatible - but this is very difficult. In my view we are actually trying to be too backwards compatible although I'm sure others would disagree with me.

I do understand the fraustration. You are quite right in your opinion.

Ok, at least I found this method is in both DNN4.9.x and DNN5.x.

<Obsolete("This method has replaced in DotNetNuke 5.0 by GetTabsByPortal()")> _

Public Function GetTabs(ByVal PortalId As Integer) As ArrayList