Thanx mitch for answering. However, my question was how to redirect to the default View Control. As the default control does not has a key, we cannot provide it in NavigateUrl().
However, I found out the solution. Using NavigateUrl() as is without providing any control key from anywhere in your module takes you to your default View Control. As for other view Controls, they have a key, so you can provide them in the NavigateUrl() method.
However, as we discussed it on your forums also, at any point of time while providing a Control key to NavigateUrl(), you also have to provide the unique Module Identifier (ModuleID) of your Module, otherwise DNN does not know in which module to look for the control, and renders a Blank screen.
That can easily be corrected as you showed above by using a ModuleID parameter to NavigateUrl(), but when you do that, only your View Control gets rendered without other modules on the page that also come with the default View Control of your module.
The only solution I have found out to this solution is to load your View Controls dynamically (you can also do this with your Edit controls if you want other Modules to remain visible with your Edit Control). DNN assumes that by default, Editing is a sensitive task, and user should concentrate only on Editing the current module at a time, so it does not render other modules, which causes a problem with other View Controls also.
Dynamic loading is the only solution, which is not very difficult. The method has been presented in the second post above, as well as in Michael Washington's adefwebserver.com DNN Help site, which I should confess is very helpful, and helped me a lot to speed my my DNN learning curve. Only wished Michael had a forum or atleast some feedback system there, where users can request additional tutorials (if not a full-fledged forum)!!!