Member Avatar for vipinsgangwar

Hi all.
I ahve an application in which ajax is used.
when i upload the publish of the application it is not working.

and if i upload the code, its working,

can nayone tell that what is the problem.


Thanks In advance

  • 2 Contributors
  • 2 Replies
  • 74 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by vipinsgangwar

Dani AI

Generated

The scenario described by (AJAX works on the development machine but not after publishing) plus 's question about AJAX extensions points to deployment/environment differences rather than page code. The usual causes are missing handlers or assemblies on the server, IIS configuration differences, or blocked/missing client script resources. The checklist below targets the specific, verifiable things to inspect when an ASP.NET AJAX site works locally but fails after publish.

  • Use the browser Network tab to find failed requests (look for ScriptResource.axd, WebResource.axd or missing .js files) and note the exact HTTP status codes (404, 403, 500).
  • Verify a ScriptManager is present (page or master) and that any CDN/scriptMode settings are reachable from the host.
  • Confirm the server has the correct .NET version or that required AJAX assemblies (System.Web.Extensions when applicable) are in the bin folder if the host does not provide them.
  • Check web.config for the system.web.extensions entries and the correct handler/module registrations: system.web/httpHandlers and system.webServer/handlers (IIS7+ Integrated vs Classic pipeline differences matter).
  • Ensure URL rewriting, security modules or host rules are not blocking .axd or .js requests and that file permissions allow the web server to serve script files.
  • If you used precompile/publish options, republish with “include all files” or copy the bin and script folders to ensure nothing was omitted.

For diagnostics, temporarily enable full error details on a staging site (customErrors off, compilation debug=true) to capture server-side exceptions, check IIS and event logs for assembly or handler errors, then revert debug settings. Capture exact failing URLs and HTTP codes — they are the most reliable clues for correcting handler mappings or missing assemblies.

Recommended Answers

All 2 Replies

Member Avatar for greeny_1984

hi,
did u add ajax extensions in your site.

Member Avatar for vipinsgangwar

yes i have added.
its working on local system but publish is not working when it is uploaded

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.