1. New a website. Open default.aspx in DV
2. Add AjaxControlToolkit.dll to the toolbox
3. Add a GridView control.
4. Turn to Template editing mode. Add a button to the template
5. Add HoverExtender, and RoundedCornersExtender to the button control via the chrome link: "Add Extender...").
6. Go to the SV and examine the gridview markup.
ACTUAL:
No extender markups
EXPECTED:
Should see markup for these extenders.
7. Now if we add more asp controls in the template, it doesn't show in SV.
Comments:
By JoDavis
The problem is the default markup for HoverMenuExtender includes two attributes, OnHide="" and OnShow="". That attribute causes an error parsing the control, and that prevents us from setting new template content. This is a Framework limitation. Templates are represented by ITemplate properties on the control, and these can only contain properly parsed controls.
This needs to be fixed in the AjaxControlToolkit. There's no way for VWD to work around it.
Incidentally, you get the same behavior if you put any error control in a template, like this:
1) Paste the following content in source view:
<asp:GridView runat="server" ID="GridView1"></asp:GridView>
<asp:Button runat="server" ID="Button1" Text="Button" Text="Button"/>
2) Switch to DV. Notice the Button has a control error because of teh duplicate Text attributes.
3) Turn to Template editing mode on the GridView.
4) Drag the Button error into the GridView's template
ACTUAL:
The Button markup never shows up in SV. If using a debug build, you get an assertion failure when the template update fails.
There's no way for VWD to work around that, either.
Comments: This ticket was filed for a pre-15.1 version of AJAX Control Toolkit. If this is still an issue in v15.1 or later, please create a new inquiry.
2. Add AjaxControlToolkit.dll to the toolbox
3. Add a GridView control.
4. Turn to Template editing mode. Add a button to the template
5. Add HoverExtender, and RoundedCornersExtender to the button control via the chrome link: "Add Extender...").
6. Go to the SV and examine the gridview markup.
ACTUAL:
No extender markups
EXPECTED:
Should see markup for these extenders.
7. Now if we add more asp controls in the template, it doesn't show in SV.
Comments:
By JoDavis
The problem is the default markup for HoverMenuExtender includes two attributes, OnHide="" and OnShow="". That attribute causes an error parsing the control, and that prevents us from setting new template content. This is a Framework limitation. Templates are represented by ITemplate properties on the control, and these can only contain properly parsed controls.
This needs to be fixed in the AjaxControlToolkit. There's no way for VWD to work around it.
Incidentally, you get the same behavior if you put any error control in a template, like this:
1) Paste the following content in source view:
<asp:GridView runat="server" ID="GridView1"></asp:GridView>
<asp:Button runat="server" ID="Button1" Text="Button" Text="Button"/>
2) Switch to DV. Notice the Button has a control error because of teh duplicate Text attributes.
3) Turn to Template editing mode on the GridView.
4) Drag the Button error into the GridView's template
ACTUAL:
The Button markup never shows up in SV. If using a debug build, you get an assertion failure when the template update fails.
There's no way for VWD to work around that, either.
Comments: This ticket was filed for a pre-15.1 version of AJAX Control Toolkit. If this is still an issue in v15.1 or later, please create a new inquiry.