Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Multiple asp.net ajax enabled modules on a pageMultiple asp.net ajax enabled modules on a page
Previous
 
Next
New Post
11/25/2006 9:16 AM
 
Stefan Kamphuis


Stefan Kamphuis's Avatar

www.40fingers.net/
Joined: 11/30/2003
Posts: 427
Hi,

I'm creating a module that uses asp.net Ajax (formerly named Atlas). It works fine, but not when I put 2 instances of the module on a page. The first module gets processed fine, but on the second, the controls on the updatepanel are not being initialized (they're "Nothing").

Any ideas on how to get this working?

Thanks in advance.
Web applications, DNN websites, modules, skins and support
 
New Post
11/26/2006 1:34 PM
 
kevin buckley

Joined: 12/16/2005
Posts: 66

The problem probably has to do with the fact that you can only have one script manager on a page.

I've been thinking about this and there are probably two ways you can handle this.

If your modules are not for resale you could look at adding the script manager to the default aspx page. I don't see why that wouldn't work.

Another thing I was thinking of trying was dynamicly adding a script manager to a page if it doesn't exist in the page controls.

I haven't tried either but they should both work in theory.

I kinda of think it would be a good idea to have support for this AJAX toolkit built into DNN once it is no longer beta. So it's a little easier to use/deploy in module development.

There is a client API in DotNetNuke, I don't know if it has it's own version of the updatepanel that you can use.
 
New Post
11/27/2006 5:06 AM
 
Matthew Christenson

Joined: 10/19/2006
Posts: 164
kbnhus wrote

The problem probably has to do with the fact that you can only have one script manager on a page.

I've been thinking about this and there are probably two ways you can handle this.

If your modules are not for resale you could look at adding the script manager to the default aspx page. I don't see why that wouldn't work.

Another thing I was thinking of trying was dynamicly adding a script manager to a page if it doesn't exist in the page controls.

I haven't tried either but they should both work in theory.

I kinda of think it would be a good idea to have support for this AJAX toolkit built into DNN once it is no longer beta. So it's a little easier to use/deploy in module development.

There is a client API in DotNetNuke, I don't know if it has it's own version of the updatepanel that you can use.

 

What about using an HTTM Module to catch the callback?  I am not very familiar with AJAX however I've used this technique to avoid having to modify the default.aspx file in the past - it's a little bit more work to get it going; but it ends up meaning that upgrades will go better - as you're not changing any of the DNN core code.

Matt Christenson

www.RealSkydiving.com
 
New Post
12/1/2006 7:45 PM
 
kevin buckley

Joined: 12/16/2005
Posts: 66

I've never created a HTTP Modules but you need to be able to add the script manager inside of the dnn form of default.aspx.

If you can do that from a HTTP or HTTM module I guess that would work also.
 
New Post
12/4/2006 11:28 AM
 
Adam

Joined: 11/9/2006
Posts: 8
How would I reference the ScriptManager from my module if it is in Default.aspx?   I tried the following but it says it doesnt exist-

 protected void Page_Load(System.Object sender, System.EventArgs e)
        {
            ScriptManager1.RegisterAsyncPostBackControl(RadioButtonList1);
         
           

        }
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Multiple asp.net ajax enabled modules on a pageMultiple asp.net ajax enabled modules on a page


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out