Comments for Tony Sneed's Blog

Comment on Type-Safe Two-Way Data Binding with INotifyPropertyChanged by sdsdsd

sdsdsd — Wed, 08 Feb 2012 16:30:26 +0000

good
explanation given
thank you very much

Comment on Digging into WCF REST by Syed

Syed — Tue, 07 Feb 2012 18:00:00 +0000

Thanks Tony,
You missed the article link…

Comment on Digging into WCF REST by Tony Sneed

Tony Sneed — Tue, 07 Feb 2012 17:38:32 +0000

My take on this is that you would have one set of entities with data contracts and are returned by WCF REST services. You would then have another set of domain entities which encapsulate your business model and domain logic. Here is an article that might help:

Comment on Digging into WCF REST by Syed

Syed — Tue, 07 Feb 2012 10:18:20 +0000

Brilliant article and well illustrated.
I am thinking WCF REST in the domain driven design (DDD). Do you have some demo for it or how we can apply above SampleService in the DDD?

Thanks
Syed

Comment on EF4 compared to NHibernate by test

test — Tue, 31 Jan 2012 06:05:21 +0000

NH allows you add a lot of garbage code and garbage files.

you dont have to worry about that in EF cause theres only 1 file …. forever .. amazing

Comment on MVVM: Simple is Beautiful by Adolfo

Adolfo — Mon, 30 Jan 2012 19:08:48 +0000

Thanks one more time, you’ve been very helpful!

Comment on MVVM: Simple is Beautiful by Tony Sneed

Tony Sneed — Mon, 30 Jan 2012 14:14:05 +0000

Yes, this will work. Person inherits from ModelBase, so m would show properties of the Person class, which is not what you want to do in the Employee class. To solve that, you need to call NotifyPropertyChanged(m => this.EmployeeID). Glad you’re on your way!

Comment on MVVM: Simple is Beautiful by Tony Sneed

Tony Sneed — Mon, 30 Jan 2012 14:10:07 +0000

If you inherit Person from ModelBase, then Employee can inherit from Person and does not have to inherit from ModelBase. As long as ModelBase is at the bottom of your inheritance hierarchy, then you don’t have to implement INotifyPropertyChanged from any of your classes and the protected NotifyPropertyChanged method will be available to all subclasses.

Comment on MVVM: Simple is Beautiful by Adolfo

Adolfo — Sun, 29 Jan 2012 21:25:27 +0000

Never mind. I already found my answer, here is how I implemented my property in my derived class (Employee):

public String EmployeeID
{
get
{
return _employeeId;
}
set
{
_employeeId = value;
NotifyPropertyChanged(m => this.EmployeeID);
}
}

Before I was using NotifyPropertyChanged(m => m.EmployeeID); but m was refering to my base type Person so it didn’t find Emlpoyee property. But that simple fix took care of it. This will get me going now. Thanks again for all your help! I’ll keep having fun with your framework.

Comment on MVVM: Simple is Beautiful by Adolfo

Adolfo — Sun, 29 Jan 2012 21:10:41 +0000

Excellent, I will watch the videos and thanks for this valuable information. The problem I see now with inheriting from ModelBase is that my classes already inherit from other classes and C# does not allow multiple inheritance. How would you use the ModelBase class when having deep class hierarchies?. Like my example I have a Person base type and Employee which inherits from Person. I can make Person inherit from ModelBase but Employee can’t since it already inherits from Person and ModelBase is strongly typed so it doesn’t have access to local Properties…..