Back to list
Views:   0
Replies:  0
Reply 1
You should handle this differently.  Having a view model is a best practice, but you should instead make a property that is of type List<Photo>.  If you also have a property for a single Photo object, then you can use this view model for both lists, and details.  And your page declaration can remain as you have shown.

public class PhotosModel  
   public List<Photo> PhotoList { get; set; }  
   public Photo Photo { get; set; }  

I hope this helps.
King Wilder, Jul 24, 2011
Stay Inspired!
Join other developers and designers who have already signed up for our mailing list.
Terms     Privacy     Licensing       EULA       Sitemap      
© Data & Object Factory, LLC.
Made with    in Austin, Texas