WPF

ObservableCollection<DADirective> listdata;
        DADirective SelectDirective;
 public void LoadDirective()
        {
            //DerivedAttributeEntity oDAEEntity;
            listdata = new ObservableCollection<DADirective>();
            
            SelectDirective = (DADirective)lbDirectiveList.SelectedItem;
            
            listdata.Add(new DADirective { DirectiveName = "Filter trading account", DirectiveDescription = "Rows will Trading account value to be filtered" });
            listdata.Add(new DADirective { DirectiveName = "Filter Counter party rows", DirectiveDescription = "Rows where counter party is null will be filtered" });
            listdata.Add(new DADirective { DirectiveName = "Filter USD currency records", DirectiveDescription = "Filter those rows where currency is USD" });

            lbDirectiveList.ItemsSource = listdata;           
        }

Ian Shlasko wrote:

I agree that using "http" as the prefix is kind of silly (I'm guessing there was
some sort of reason for it, but not looking it up right now)... But it
works.

devvvy wrote:

you think it's worthwhile?

<br />
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"<br />
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" <br />
xmlns:Infra="http://infragistics.com/DockManager" <br />
xmlns:MyLib1="clr-namespace:AbcFirm.Lib1"<br />
xmlns:MyLib2="clr-namespace:AbcFirm.Lib2" <br />
xmlns:MyLib3="clr-namespace:AbcFirm.Lib3" <br />
xmlns:sys="clr-namespace:System;assembly=mscorlib"<br />

<br />
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"<br />
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"<br />

<br />
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentationXXXXX"<br />
xmlns:x="http://schemas.microsoft.com/winfx/2006/xamlXXXXX"<br />
xmlns:sys="clr-namespace:System;assembly=mscorlib"<br />

<br />
The root element also contains the attributes xmlns and xmlns:x. These attributes indicate to a XAML processor which XAML namespaces contain the type definitions for backing types that the markup will reference as elements. The xmlns attribute specifically indicates the default XAML namespace. Within the default XAML namespace, object elements in the markup can be specified without a prefix. For most WPF application scenarios, and for almost all of the examples given in the WPF sections of the SDK, the default XAML namespace is mapped to the WPF namespace http://schemas.microsoft.com/winfx/2006/xaml/presentation. The xmlns:x attribute indicates an additional XAML namespace, which maps the XAML language namespace http://schemas.microsoft.com/winfx/2006/xaml. <br />

<br />
xmlns:MyLib1="clr-namespace:AbcFirm.Lib1"  <br />
xmlns:MyLib2="clr-namespace:AbcFirm.Lib2" <br />
xmlns:MyLib3="clr-namespace:AbcFirm.Lib3" <br />
xmlns:sys="clr-namespace:System;assembly=mscorlib"<br />
xmlns:igDock="http://infragistics.com/DockManager"  << NOTE: You don't necessarily need to use "clr-namespace", you can rely on [assembly: XmlnsDefinition] instead)<br />

<br />
[assembly: XmlnsDefinition("<a href="http://infragistics.com/DockManager">http://infragistics.com/DockManager</a>[<a href="http://infragistics.com/DockManager" target="_blank" title="New Window">^</a>]", "...InfragisticDockPanel...")]<br />

devvvy wrote:

xmlns:MyLib1="clr-namespace:AbcFirm.Lib1" < Cool, no useless Url's

devvvy wrote:

xmlns:Infra="http://infragistics.com/DockManager" < Why....