Comments on: First usage of WCF and specified fields. http://thecodemonk.com/2009/04/27/first-usage-of-wcf-and-specified-fields/ Random Thoughts of a Software Development Professional Wed, 11 Jan 2012 18:22:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Joe http://thecodemonk.com/2009/04/27/first-usage-of-wcf-and-specified-fields/comment-page-1/#comment-126 Joe Sun, 28 Nov 2010 01:25:05 +0000 http://thecodemonk.com/?p=37#comment-126 OK, I'm not using Linq in my project... so I'm guessing your classes are based on Linq classes which themselves implement INotifyPropertyChanged? I'm not familiar with Linq. I don't know your email address so if you could shoot me an email I'd like to take this up with you further. I'd very much like to implement this functionality in my app. Thanks! OK, I’m not using Linq in my project… so I’m guessing your classes are based on Linq classes which themselves implement INotifyPropertyChanged? I’m not familiar with Linq.

I don’t know your email address so if you could shoot me an email I’d like to take this up with you further. I’d very much like to implement this functionality in my app. Thanks!

]]> By: TheCodeMonk http://thecodemonk.com/2009/04/27/first-usage-of-wcf-and-specified-fields/comment-page-1/#comment-125 TheCodeMonk Sun, 28 Nov 2010 00:46:10 +0000 http://thecodemonk.com/?p=37#comment-125 Joe - The only place that INotifyPropertyChanged is used is in my Linq to SQL classes. You can write them up in any custom classes, but beware, the code will only work server side. On the client side, methods and property code will not be included in the project that creates the service reference to your WCF service. They turn into dumb classes with simple properties that can be get and set. Think of it this way.. The classes that are public on the service are just dumb classes that you can pass data back and forth with in the service. Any custom code in those classes will not execute until that data is sent to the service and a new object is instantiated and the data is set in this object and then your property changed event can be fired. If I am not clear, or misunderstood, feel free to contact me via e-mail. Joe – The only place that INotifyPropertyChanged is used is in my Linq to SQL classes. You can write them up in any custom classes, but beware, the code will only work server side. On the client side, methods and property code will not be included in the project that creates the service reference to your WCF service. They turn into dumb classes with simple properties that can be get and set.

Think of it this way.. The classes that are public on the service are just dumb classes that you can pass data back and forth with in the service. Any custom code in those classes will not execute until that data is sent to the service and a new object is instantiated and the data is set in this object and then your property changed event can be fired.

If I am not clear, or misunderstood, feel free to contact me via e-mail.

]]> By: Joe http://thecodemonk.com/2009/04/27/first-usage-of-wcf-and-specified-fields/comment-page-1/#comment-124 Joe Sat, 27 Nov 2010 23:27:43 +0000 http://thecodemonk.com/?p=37#comment-124 I'm trying to implement your idea but I think you left out a couple details. Are you implementing the INotifyPropertyChanged interface in one of these classes? Because the PropertyChanged event handler needs to be declared somewhere. How did you rig that up? Thanks. I’m trying to implement your idea but I think you left out a couple details. Are you implementing the INotifyPropertyChanged interface in one of these classes? Because the PropertyChanged event handler needs to be declared somewhere. How did you rig that up? Thanks.

]]>