well you can set IE controls... TabStrip exactly to do a postback... in the
postback you can check for the SelectedIndex and post it to whatever aspx
name you need to.
its not the most elegant way but it sure does the job.
private void tsNav_SelectedIndexChange(object sender, System.EventArgs e)
{
SetNav();
}
private void SetNav()
{
switch(tsNav.SelectedIndex)
{
case 0:
myLoader.Attributes.Add("src", "CA_ShowEarlyBird.aspx");
break;
case 1:
myLoader.Attributes.Add("src", "CA_ShowCategories.aspx");
break;
case 2:
myLoader.Attributes.Add("src", "CA_ShowSubCategories.aspx");
break;
case 3:
myLoader.Attributes.Add("src", "CA_ShowAvailableColors.aspx");
break;
case 4:
myLoader.Attributes.Add("src", "CA_ShowAvailableSizes.aspx");
break;
case 5:
myLoader.Attributes.Add("src", "CA_ShowProducts.aspx");
break;
case 6:
Response.Redirect("~/Signout.aspx");
break;
}
}
and it sure does work....
--
Regards,
HD
Once a Geek.... Always a Geek
"Kenneth" <an*******@discussions.microsoft.com> wrote in message
news:3A**********************************@microsof t.com...
John,
This is exactly what I mean. in www.asp.net they're referring to the ie
web ctrls and tabstrip can't handle urlnavigation to existing .aspx
documents.
The IEWebCtrls are NOT the correct answer.
/Kenneth