Same-named Public DirectMethods in multiple UserControls does not exception or warn

  1. #1

    Same-named Public DirectMethods in multiple UserControls does not exception or warn

    I used the following DirectMethod attribute (which if I understand correctly makes it public).
        [DirectMethod( IDMode = DirectMethodProxyIDMode.None, ShowMask = true )]
    And yeah, in that case there is no warning or exception if the same DirectMethod name/declaration is duplicated in multiple UserControls. I have ResourceManager.CleanResourceUrl=true in my use-case.


    See http://forums.ext.net/showthread.php...446#post123446 for details.
  2. #2
    Hi @michaeld,

    We cannot determine it in all the cases. User controls can be rendered dynamically. How can we know there is already such a DirectMethod on client? Maybe, we could store a list of rendered DirectMethods on server and check it before rendering a new one. But is it really worth to do that?

    If a developer uses
    IDMode = DirectMethodProxyIDMode.None
    he should be aware that it will be overridden. As you are.
  3. #3
    Honestly, yeah, this isn't that big a big deal. Though I still think it would be really great if each control with the same public name did raise its own postback.

    I thought you had wanted me to post this in a separate thread.
  4. #4
    Added to the Agenda of our next team meeting.

Similar Threads

  1. Replies: 0
    Last Post: Nov 12, 2013, 9:08 PM
  2. [CLOSED] Dynamic UserControls with DirectMethods
    By JulianPreece in forum 2.x Legacy Premium Help
    Replies: 3
    Last Post: Sep 13, 2012, 10:50 AM
  3. Replies: 3
    Last Post: Jul 02, 2012, 9:27 AM
  4. Replies: 11
    Last Post: Jun 22, 2012, 7:10 PM
  5. [CLOSED] Multiple UserControls, Column and Tabs
    By CMA in forum 1.x Legacy Premium Help
    Replies: 5
    Last Post: Jan 15, 2010, 1:09 PM

Posting Permissions