1. <LI>The Enum type of window.TriggerEvent property has changed from TriggerEvent to HtmlEvent.

    Example (Old)
    Window1.TriggerEvent = TrigerEvent.Click;

    Example (New)


    Window1.TriggerEvent = HtmlEvent.Click;
    The markup syntax has not changed.

    Example


    <ext:Window runat="server" TriggerEvent="Click" />
    Several new html events added including:

    i. Abort
    ii. Submit
    iii. Unload</LI>
    <LI>The default value for the window.CloseAction property has changed from CloseAction.Close to CloseAction.Hide. Now by default Windows will not be destroyed when closed.

    In general, developers should not have to change their existing project source code. If the property is explicitly being set to CloseAction.Hide, then that property can be removed, but is optional.</LI>
    <LI>The TokenID format has changed from "{ControlID}" to "#{ControlID}".

    Example (Old)

    <Listeners>
        <Click Handler="{Panel1}.expand();" />
    </Listeners>

    Example (New)


    <Listeners>
        <Click Handler="#{Panel1}.expand();" />
    </Listeners>
    The TokenID will be parsed and replaced with the .ClientID of the control it references. All Coolite Toolkit controls are instantiated client-side using their .ClientID. The .ClientID may be different than the controls .ID property if the control is rendered within an INamingContainer control such as a MasterPage. </LI>
    <LI>The <ext:Hidden> and <ext:ScriptManager> "Hide" property have been renamed to "HideInDesign". The "HideInDesign" property will hide the control when Visual Studio is in Design-Mode. The property has no affect on any runtime rendering of the control.

    The "Hide" was renamed to avoid confusion with the "Hidden" property and the .Hide() Method, both of which "hide" the control when rendered in the browser.

    If the control is "hidden" at runtime, it's still available in the DOM just as through it was not hidden. Any JavaScript run against a hidden control will continue to work as expected and no JavaScript error will be thrown. The control is still there... it's just "hidden", kind of like "The Invisble Man".</LI>
    <LI>The .ActiveTab property has changed.

    In previous versions the .ActiveTab property was an 'int' type, but has now been changed to a type of 'Tab'.

    The following sample demonstrates how to set the ActiveTabIndex in markup.

    Example (old)

    <ext:TabPanel 
        ID="TabPanel1"
        runat="server"
        ActiveTab="1"
        Title="Title">
    Example (new)

    <ext:TabPanel
        ID="TabPanel1"
        runat="server"
        ActiveTabIndex="1"
        Title="Title">
    The new .ActiveTabIndex property has been added to replace the previous .ActiveTab functionality.

    The .ActiveTab property is now used in code-behind to programatically get/set an instance of the active tab.</LI>
    <LI>The <ext:Window> .TriggerElement property has been removed.

    Please "show" the Window by using the <Listeners> or <AjaxEvents> on the launching element/control.

    Example (Listener)

    <ext:Button ID="Button1" runat="server" Text="Show Window">
        <Listeners>
            <Click Handler="Window1.show()" />
        </Listeners>
    </ext:Button>
    Example (AjaxEvent)

    <script runat="server">
        protected void Button_Click(object sender, AjaxEventArgs e)
        {
            this.Window1.Show();
        }
    </script>
    
    <ext:Button ID="Button1" runat="server" Text="Show Window">
        <AjaxEvents>
            <Click OnEvent="Button1_Click" />
        </AjaxEvents>
    </ext:Button>
    </LI>
    <LI>The <ext:Window> .TriggerEvent property has been removed.

    See above #6. Now any Listener or AjaxEvent from any element/component can "trigger" an event to fire.</LI>
    <LI>The default value of the <ext:Button> .AutoPostBack property has been changed from "true" to "false".

    In Visual Studio DesignMode, double clicking on the <ext:Button> will automatically wire up the "OnClick" event handler, but as with other postback enabled controls, such as <asp:TextBox>, the developer will now have to explicitly set the .AutoPostBack property to "true".

    Please see the following forum post for more information, see http://forums.ext.net/showthread.php?postid=2044.aspx

    </LI>