Member Avatar for mania_comp

Hi..
I want to use SlideShowExtender in my website.
For that I have created testing website. But its not working. I have tried both ways of defining GetSlides() method in same page as well as in WebSerice.
But none of them is working..
I have attached my sample website in zip format..
If someone can test it and point out the error it will be a great help to me.

Thank You for your time.
Cheers

SlideShow.zip (313.65 KB)
  • 2 Contributors
  • 2 Replies
  • 88 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by mania_comp

Dani AI

Generated

— since you tried both a page method and an .asmx and already pointed you to the toolkit binary, the next thing is a focused checklist of the usual environmental and integration problems that make SlideShowExtender appear to “not work.” The items below are practical, verifiable steps to isolate the cause without changing your whole project.

  • Verify a ScriptManager is on the page (the extender requires client script support). A minimal declaration:

    <asp:ScriptManager runat="server" />

    You may also use the ToolkitScriptManager provided by the toolkit, but ScriptManager present is the key.

  • Confirm assembly/version compatibility. The AjaxControlToolkit.dll in the bin must match the project target framework (3.5 vs 4.x). Avoid having multiple copies (bin + GAC) or mismatched releases; using the official build from the toolkit repository or NuGet ensures a correct build.

  • Check the slide service method and how it is exposed. For an .asmx service the class should be decorated with [System.Web.Script.Services.ScriptService] and the method with [WebMethod]. For a page method it must be static and marked [WebMethod]. The method must return the JSON structure the extender expects (an array of slide records).

  • Use browser dev tools: open the Console and Network tabs. Look for JavaScript errors like “Sys is undefined” or a failing request to the slide service (404/500). A 404 means the ServicePath/ServiceMethod (or URL) is wrong; a 500 means a server exception — view the response body or turn off custom errors to see details.

  • Check web.config and references: ensure system.web.extensions is compatible, compilation debug=true for easier errors, and no assembly binding redirects are breaking the toolkit.

If the above items are all correct, try a minimal single-page repro (ScriptManager + one Image + SlideShowExtender + tiny service) copied from the toolkit examples to confirm the environment. Official sources and examples are available from the AjaxControlToolkit repository and Microsoft ScriptManager docs: AjaxControlToolkit on GitHub and ScriptManager documentation.

Recommended Answers

All 2 Replies

Member Avatar for kvprajapati

Please download .

Member Avatar for mania_comp

Thank you for your advice but I have already installed AjaxToolkit..
My AjaxToolkit.dll ib bin folder has version 1.0...
It was working with same dll in an online website..
But I have created new project using same dll and its not working..
Why?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.