Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you're using the <code>asp:ScriptManager</code> control, try using the <code>ajaxToolkit:ToolkitScriptManager</code> control instead.</p> <p>I put together a test project and when using the <code>asp:ScriptManager</code> the <code>TabPanel</code> wouldn't display, though they were in the source html. I was also getting a javascript error, 'Sys.Extended is undefined', which led to numerous web search results spanning multiple versions of the ajax toolkit. A common suggestion was to switch script managers. Doing so fixed the visibility of the <code>TabPanel</code> and eliminated the javascript error as well. </p> <p>Specifics of test project:<br/> VS2010<br/> ASP.Net web app using .Net 4<br/> IIS Express<br/> Installed AjaxControlToolkit version 4.1.7.725 using Nuget<br/> TabContentTemplateTest.ascx identical to code and markup in original question<br/> Default.aspx codebehind identical to code in original question<br/> Default.aspx markup as follows</p> <pre><code>&lt;%@ Page Title="Home Page" Language="C#" MasterPageFile="~/Site.master" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="WebGUI.Default" %&gt; &lt;asp:Content ID="HeaderContent" runat="server" ContentPlaceHolderID="HeadContent"&gt; &lt;/asp:Content&gt; &lt;asp:Content ID="BodyContent" runat="server" ContentPlaceHolderID="MainContent"&gt; &lt;ajaxToolkit:ToolkitScriptManager runat="server" ID="ajaxScriptManager" /&gt; &lt;ajaxToolkit:TabContainer runat="server" ActiveTabIndex="0" ID="SamplesTabContainer"&gt; &lt;/ajaxToolkit:TabContainer&gt; &lt;/asp:Content&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload