Using tabbar with ASP.Net MasterPage and ContentPage

Suite and Optimus Suite 5
#1

Hullo,



What I’d like to do is set up a tabbar control in an ASP.Net 2.0 MasterPage. I’d like it so that when the user clicks a tab, the respective content page is loaded into the asp:ContentPlaceHolder control.



I’ve found this post: dhtmlx.com/docs/products/kb/ … ssr=yes&s=[tabbar]



but using the ajax-html method produces some weird results: clicking on a tab seems to load the both the masterpage and and content page inside the div that the tabbar control lives in. This that there suddenly appears to be another tabbar control immediately beneath the original …



Here is the code I have in my MasterPage.Master file:


<asp:ContentPlaceHolder ID=“MainContentHolder” runat=“server”>



</asp:ContentPlaceHolder>






The content pages simply have dummy text in for the time being; example:



<%@ Page Language=“vb” AutoEventWireup=“false” MasterPageFile="~/MasterPage.Master" CodeBehind=“Information.aspx.vb” Inherits=“TestSite.DSSMSSABInfo”

title=“Information Page” %>

<asp:Content ID=“Content1” ContentPlaceHolderID=“MainContentHolder” runat=“server”>

Just some filler information, nothing to see here…

</asp:Content>





Is there a better approach?

#2


Hello,


In case of ajax-html mode, content is loaded from a server and placed into a tab - and nothing else.


It is hard to reproduce the described problem locally. Please, provide a direct link to problematic page (also you can send it to support@dhtmlx.com) - we’ll try to help.

#3

I see.  I tried sending a sample zipped project, however the Gmail filters seemed to block most of the files…

#4


Hello,


we received your sample and sent the answer by email.

#5

I received your file and took a look at it.  I appreciate and thank you for your time in assisting me with this issue. Unfortunately those html files will not work in our ASP.Net project.  It seems as you pointed out that the tabbar control and content are loaded into the same div.  It simply seems impossible to use this control with Master and Content pages… 

However should we ever need to develop a non ASP.Net site this control will definitely be used.