WPF

Kevin Marois wrote:

How do you unit test a piece of UI becoming visible/invisible? The bound bool may be correct, but the converter could fail.

Kevin Marois wrote:

How do you unit test data validations?

Pete O'Hanlon wrote:

(this is assuming you aren't using the standard visibility converter

zahalul wrote:

Can you please send a C# code ?

     <StackPanel x:Name="grd">

        <ListView x:Name="listView">
            <ListView.View>
                <GridView>
                    <GridViewColumn Header="Severity" DisplayMemberBinding="{Binding Icon}"/>
                    <GridViewColumn Header="Id" DisplayMemberBinding="{Binding Id}"/>
                    <GridViewColumn Header="Name" DisplayMemberBinding="{Binding Name}"/>
                    <GridViewColumn Header="Immagine" >
                        <GridViewColumn.CellTemplate>
                            <DataTemplate>
                                <Image Source="{Binding ImagePath}" />
                            </DataTemplate>
                        </GridViewColumn.CellTemplate>
                    </GridViewColumn>
                </GridView>
            </ListView.View>
        </ListView>
     </StackPanel>
</Window>

public partial class MainWindow : Window
    {
        public class MyItem
        {
            public string Icon { get; set; }

            public int Id { get; set; }

            public string Name { get; set; }

            public string ImagePath { get; set; }       
        }

        public MainWindow()
        {
            InitializeComponent();

            MyItem Item = new MyItem();

            Item.Icon = "1";
            Item.Id = 0;
            Item.Name = "Zvika";
            Item.ImagePath = "icon1.png";
            this.listView.Items.Add(Item);
        }

     }

Mycroft Holmes wrote:

Entityframework is the work of satan, it wraps up your data management and ORM into a black box and then feeds you the nice, sanitised data titbits. It also tries to do everything for everyone and is therefore a monster.

You end up with a programmer who knows how to use EF but does not understand the underlying data management or how the ORM works and how he got his sanitised object. When it does go wrong they will try and work around it withing the EF structure, not understanding the fundamental problem that caused the error!

Mycroft Holmes wrote:

If you do not need a database (you will for your production system) are yo even contemplating including EF in you project.

_T_C_ wrote:

Are you implying that Entity Framework only merits contemplation when a database is required?