DataView name conflict

  1. #1

    DataView name conflict

    Given that System.Data has DataView class and that System.Data is commonly a default imported namespace, renaming the Coolite.Ext.Web.DataView would, in my opinion, be a good move.
  2. #2

    RE: DataView name conflict

    Hi Justin,

    We can't rename the DataView control, but I can offer a couple options to work around any nameing conflicts.*


    Modified using statement:


    using DataView = Coolite.Ext.Web.DataView;

    Using the fully qualified namespace:


    Coolite.Ext.Web.DataView view = new*Coolite.Ext.Web.DataView();

    Hope this helps.


    Geoffrey McGill
    Founder
  3. #3

    RE: DataView name conflict



    I understand renaming the class is not really feasable now, I was coming at
    it more from the side of having to use the fully qualified namespace
    System.Data.DataView everywhere (I don't use Coolite DataView anywhere at
    present). Anyway, was just a thought.</p>


    </p>

    (Also IE8 isn't letting me post here - get "The board administrator has requested that you must provide some message
    content within your post. You cannot post only HTML, Images, EmotIcons or
    IFCode." - don't know if that's just me as first time using IE in a while)</p>

Similar Threads

  1. [CLOSED] DataView to DataView Drag and Drop
    By paulc in forum 2.x Legacy Premium Help
    Replies: 1
    Last Post: May 10, 2012, 8:19 PM
  2. Style sheet conflict
    By Dallas Morrison in forum 1.x Help
    Replies: 3
    Last Post: Feb 20, 2012, 3:43 AM
  3. Namespace Conflict for Class X?
    By mbean in forum 1.x Help
    Replies: 9
    Last Post: May 25, 2011, 1:31 PM
  4. GridFilter conflict with Paging Toolbar
    By BeroOo in forum 1.x Help
    Replies: 5
    Last Post: Aug 19, 2010, 12:45 PM
  5. [1.0] Possibility of future conflict with core ExtJs
    By r_honey in forum Open Discussions
    Replies: 2
    Last Post: Jan 07, 2010, 1:38 PM

Posting Permissions