DNN Ver: 05.06.07

We just upgraded from 05.06.01, and the Globals.NavigateUrl(tabId) method not longer works... it just returns the URL of the portal the user is currently on, and disregards the tabid parameter.

The code is pretty straight forward:

Response.Redirect(Globals.NavigateUrl(objCustomUser.TabId), true);

Nothing happens in the browser. I've verified that TabId is the right id (for another portal) but the user isn't taken there. As a workaround, I tried using Globals.ApplicationURL(TabId), and that works, but the URL isn't as nice and neat, and I'm sure someone will complain.

Any suggestions? Is this a known issue?

The TabId that's being passed in is a HomeTabId property in the DotNetNuke.Entities.Portals 
PortalInfo object. Here's what we have, which worked prior to the upgrade:

PortalInfo objPortal = objPortalController.GetPortal(objUser.PortalID);
Response.Redirect(Globals.NavigateURL(objPortal.HomeTabId));

I've verified that objPortal.HomeTabId is the TabId for the other portal, however the NavigateUrl() method is returning the URL for the same portal. Users are logging in at this address:
http://dev.MyWebsite.com/PortalLogin/Home/tabid/4603/Default.aspx

Code called, where HomeTabId = 3244:
Response.Redirect(Globals.NavigateURL(objPortal.HomeTabId));  

...and are being redirected back to the same portal
http://dev.MyWebsite.com/PortalLogin/Home.aspx

I'm wondering if there's another way to redirect users to the correct portal with a more "friendly" Url (ie one that uses Portal name rather than a querystring)?

Thanks again William, I appreciate all the research!