Hi,

Work around. This is not a best but will work (would be great to add the ref to default.aspx page from the module code)

Steps:
 
1. Download attached AjaxControlToolkit.dll_ and rename it to AjaxControlToolkit.dll and put into the DNN bin folder. Or you can download a copy of it from the microsoft site, upto you.
 
2. Open your DNN module project and add reference to the above AjaxControlToolkit.dll and build your project (depends on your project setup, your dll will be copied to DNN bin folder). I have noticed following changes in main web.config file
 
<dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
 
 
3. As DNN is using its own ScriptManager rather than the ToolkitScriptManager, so the work arround for it (not a best option, unless dynamically you can do it from your module code, have not found enough time to play with this):
 
 - open DNN default.aspx page and add following code
<asp:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server">
</asp:ToolkitScriptManager>
 
just after  <dnn:Form id="Form" runat="server" ENCTYPE="multipart/form-data" >
 
4. Delete any web.config from you module folder, which is under "DesktopModules".
5. Open DNN website and load your module, it should work.
 
Hope this helps.

******************************************
Regards
Latiful Khan