Hi Jim,
You don't want to do that. That way if you modify the TabStrip, you will have to modify the TabStrip control in each content page, which defeats the purpose of the master page.
You can use the following way to expose the TabStrip to your content page:
Step 1:
Add MasterPage directive in your content page:
Code: HTML/ASPX
<%@MasterType VirtualPath="path_of_your_master_page" %>
This allows you to access your master page from your content page in a strong typed manner.
Step 2:
Expose the TabStrip from the master page:
Code: C#
public partial class MasterPage: System.Web.UI.MasterPage
{
.....
public EO.Web.TabStrip MainTabStrip
{
get { return TabStrip1; }
}
.....
}
This is necessary since by default TabStrip1 is "protected", you will need to expose it as a "public" member in order for the content page to access it.
Now you can access the TabStrip from your content page:
Code: C#
Master.MainTabStrip.SelectedIndex = 1;
It's possible for you to hook up event handler this way, but I wouldn't recommend it because Visual Studio Web Form designer does not support it --- you can do it manually but it can get messy. Generally speaking, if you have to update something (for example, a Label control Label1) in your content page from your master page, you should move that control (Label1 in this case) into your master page.
Thanks