I am badly waiting for RIA support on 4.1 model-first (LinqToEntitiesDomainContext<TContext> where TContext : DbContext - is's not supported yet).
Also, you shouldn't have to decorate your POCOs with the nasty Key attributes, the goal is to have generated POCOs that RIA processes and decorates automatically for the client (perhaps via DomainDescriptionProvider).
Anther thing I couldn't come along is how to share interface implementations over the wire, please vote for it.
My wet dream is model-first only, and this should generate database (should have more options), server entities, auto-decorated client DTOs that implement interfaces generated from POCOs (undecorated at all) + full MVVM support (i.e. relaxed while very extesible data manipulation controls for the VMs that can be (or not) exposed to the Views)
Hello Mike! I love your videos, I feel I got much wiser after watching this series.
I think it would be a great thing if you could add videos about the other features of Prism 4.0 (navigation etc.)
Also, I wish you could extend this series so that after watched and studied, user should be able to build a robust Silverlight LoB application, using other related features of Silverlight and its relatives, such as WCF RIA Services, Entity Framework, and patters like Repository, DAL and more. The final idea is to teach users how to create a real-life end-to-end LoB application using the most efficient available ways and technologies.
Take it easy brother, I just brought plain examples, forget about the specific data.
1) I would never use Dim integer = "45", I just meant that you don't need to explicitly convert anything, and yes, sometimes when you are sure that the String's value is actually an integer you don't have to pass it to another Parse function.
2) Enums in vb can be automatically used as plain integers so u can use it in some cases even to make some calculations and conditions according to the order of it, not only but I make the numbers in my enum according to the desired calculations I expect later,
u can even use bit shift if you have very large enums with key values so u make the key values 8 16 32 and use bit shift etc. again, I just brought you examples to explain what I said but the examples are not the code, so chill about it.
3-4) I don't; Instead I write comments on every line.
And no, don't learn from me, this is just my taste, and if you really want to hear, sometimes I could write
Dim x As Integer
If x Then
Console.WriteLine("x <> 0") 'Will never reach this line since x =
With the above example I mean 2 things, 1st, that integers can be evaluated as booleans, and 2nd, you can rely on the fact that integer is not nullable and bacomes automatically 0 when declaring the field.
Especially, this days that you can oficcially declare Dim x = 5 and the compiler automatically recognize it as integer and even provides full intellisense support.
I would agree with you concerning the readability issue, but I told you I am good with comments, besides I am not working with a group, so I am the one who decides about the coding conventions, and I do have strict conventions.
I would also say "Different strokes for different folks".
Personally, that's why I like VB, FLEXIBILITY!
Thanks for your post, would like further discussions
Actually I think that in Wpf when you bind data it's binded to properties only (I am not definately sure).
Donno if applying attributes on properties will work on private fields as well as exposing properties with BrowsableAttribute for the desiner in a custom control.
these examles should be checked i am not sure they're even relevant.
But as Jason said, properties became a convention of encapsulation...