my cascading drop down list is not working in the AJAX BETA 1 RELEASE,
if i have the cascading drop down list in side a form view then it is not working ,else it is working perfectly.
still not sure
oes any body has same problem????
Maybe:http://forums.asp.net/thread/1441672.aspxI checked out the instructional videos provided on this site for the Microsoft AJAX but it is all for the ATLAS release.
Take for example here is some of the code that I have from one of the videos
<%
@dotnet.itags.org.PageLanguage="VB"AutoEventWireup="false"CodeFile="Default.aspx.vb"Inherits="_Default" %><%
@dotnet.itags.org.RegisterAssembly="Microsoft.Web.Atlas"Namespace="Microsoft.Web.UI"TagPrefix="atlas" %><%
@dotnet.itags.org.RegisterAssembly="AtlasControlToolkit"Namespace="AtlasControlToolkit"TagPrefix="atlastoolkit" %><!
DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><
htmlxmlns="http://www.w3.org/1999/xhtml"><
headrunat="server"><
atlas:ScriptManagerID="PageScriptManager"runat="server"EnablePartialRendering="True"/><
atlastoolkit:HoverMenuExtenderID="HoverMenuExtender1"runat="server"><atlastoolkit:HoverMenuPropertiesTargetControlID="btnProduct"PopupControlID="PanelPopUp"PopupPosition="Left"PopDelay="25"/></atlastoolkit:HoverMenuExtender><
title>Untitled Page</title><
styletype="text/css">/*Hover Menu*/
.popupMenu
{position:absolute;visibility:hidden;background-image:url(images/header.png);opacity:.9;filter:alpha(opacity=90);}
.popupHover
{background-image:url(images/header-opened.png);background-repeat:repeat-x;background-position:lefttop;background-color:#F5F7F8;}
</
style></
head><
bodystyle="text-align: left"><formid="form1"runat="server"><br/><table><tr><tdstyle="width: 80px"><asp:PanelID="PanelPopUp"runat="server"Width="80"BackColor="white"CssClass="popupMenu"><asp:LinkButtonID="BtnUpdate"runat="server"CausesValidation="True"CommandName="Update"Text="Update"></asp:LinkButton> <br/><asp:LinkButtonID="BtnDelete"runat="server"CausesValidation="False"CommandName="Cancel"Text="Delete"></asp:LinkButton> </asp:Panel></td><tdstyle="width: 100px"><asp:LinkButtonID="btnProduct"runat="server"Width="273px">Product Number One</asp:LinkButton></td></tr></table></form></
body></
html>
Now the big issue is I just installed the new Beta 2 I do not have the ATLAS installed. I do not get any options for AJAX controls or code and I created a new website using the option for "ASP.NET AJAX-Enabled Web Site"
Please tell me what is going wrong do I need to uninstall and reinstall everything.
Also I am using the Visual Studio Express Web
Thank you for any help you can provide on this
hello.
1st, the ajax extensions have changed the prefix name used...there's a breaking change document which explains this on the ajax.asp.net site
you should also note that you need to download the toolkit pack from codeplex in order to use it...
Prior to this release I had a (?potentially bad?) habit of putting my script manager tag inside the <head> tag. Now it looks like that can't be done, or at least the intellisense won't work there. Any comments on
1) this was a stupid idea to begin with ?
2) its a bug or a feature - but get used to it?
Thanks.
hello.
1. if i'm not mistaken, now theymust be inside a form (which is good since after all we're talking about a server control)
2. well, not getting intellisense is surelly a bug :)
In the early CTPs they worked inside the head, which in 2.0 is a programmable container.
The loss of this ability to me to be a 'breaking change' from CTP to Beta. Its 'adjustable' but cuts down some scenarios for wiring in clientside scripts using web service proxies declared in the header, but meant to be used via dhtml outside of serverside form tags. Working through my scenarios now.
hello.
well, in my opinion, the previous behavior was a bug, since all server controls must be declared inside a server form.
Not all controls are required to be within the form;
The SM is required to be within the form in the beta, but this may be relaxed. The partial page postback model (UpdatePanel) requires it to be in the form, but when EnablePartialRendering is not on and/or Updatepanels are not around, then it might be 'allowed' outside. Still being debated however.
hello again.
well, from looking at the control hierarchy, i think that my previous statement was wrong since it only inherits from control. so, maybe it could be put outside the form tag (if it doesn't break the page postback model)
Currently the latest release of AJAX (1.0) was missing the validators.dll. The initial message about this talked about a windows update which had not been released yet. Now I'm wondering if the latest framework (3.0) which is available now includes the validators.dll built into it. Anyone know? I didn't see anything about this yet.
^_^
Ajax release 1.0 is an "extension" to the .NET framework 2.0
.NET 3.0 is an overlay of .NET 2.0 including the Windows Foundation stuff, mainly used in Windows Vista - which includes the WPF, WCF, WCS, and WWF
There wont be Ajax validator dlls in the .net 3.0 framework.
I'm assuming you are speaking of the System.Web.Extensions.Validators exception that gets thrown when you try to use ajax 1.0 released version.
Take the <tagMappings> section in your web.config and comment it out.
