JohnPapa.net: All Comments

RE: Why Use the Entity Framework?

Emir Treviño — Fri, 04 Jul 2008 21:14:00 GMT

Hi John, what is your opinio about this tool:

http://www.codeplex.com/sfs/

thanks

RE: Using the Entity Framework in a Layered Architecture

Dew Drop - July 4, 2008 | Alvin Ashcraft's Morning Dew — Fri, 04 Jul 2008 21:07:00 GMT

Pingback from Dew Drop - July 4, 2008 | Alvin Ashcraft's Morning Dew

Trackback url: http://www.alvinashcraft.com/2008/07/04/dew-drop-july-4-2008/

RE: Tutorial: Create a Silverlight 2 User Control from a Popup Control

Tutorial: Create a Silverlight 2 User Control from a Popup Control — Thu, 03 Jul 2008 04:31:00 GMT

Pingback from Tutorial: Create a Silverlight 2 User Control from a Popup Control

Trackback url: http://2x.morelyrics.co.uk/2008/06/19/tutorial-create-a-silverlight-2-user-control-from-a-popup-control/

RE: 6 Great Tools For Writing a Book

My Book Has a Life of its Own — Mon, 30 Jun 2008 02:52:00 GMT

I set out to write a book on data access, services, and Silverlight 2 and stick to those topics faithfully. I have a sticky note on my desk that shows the main topics and the word “thin” as a reminder to myself to stick to the point and keep the book

Trackback url: http://johnpapa.net/all/my-book-has-a-life-of-its-own/

RE: As it Once Was, I am Writing a Book

My Book Has a Life of its Own — Mon, 30 Jun 2008 02:52:00 GMT

Trackback url: http://johnpapa.net/all/my-book-has-a-life-of-its-own/

RE: Entity Framework & LINQ Tonight in Sarasota

the community foundation of sarasota county — Sun, 29 Jun 2008 18:46:00 GMT

Pingback from the community foundation of sarasota county

Trackback url: http://johnpaul.greatestluststories.com/thecommunityfoundationofsarasotacounty.html

RE: Refactoring a PropertyChanged Event Handler

John Papa — Fri, 27 Jun 2008 22:27:00 GMT

I agree that in this case I would not use partial methods. Not when there are alternatives like a base class method. But its an idea I had not thought of.

RE: Refactoring a PropertyChanged Event Handler

Jonas — Fri, 27 Jun 2008 16:46:00 GMT

At first I also thought that partial methods was too smelly, but if you think about it, you don't have to have a partial method for each property. You can have one partial method: OnPropertyChanging or OnPropertyChanged and just call that method on every setter of each property passing in both the propertyname and the value. In that case it wouldn't required a lot of code and thus no need for autogenerated code.

Performance wise I'm not sure which way is better.

RE: Refactoring a PropertyChanged Event Handler

Neil Mosafi — Fri, 27 Jun 2008 08:43:00 GMT

Oooh I wouldn't use Partial Methods for anything which wasn't codegen'd it's way too smelly!

Anyway another option I can point out is to declare the event as

public event PropertyChangedEventHandler PropertyChanged = delegate {};

Then you don't need to worry about checking for null etc because the event cannot be null. Performance hit is pretty minimal for this and you also don't have to worry about concurrency issues etc (which your base class wasn't taking care of).

Also Seb came up with a good way of doing it using DynamicProxy2 which i thought was very cool and even allows you to use it with automatic properties - serialseb.blogspot.com/.../implementing-in

RE: Refactoring a PropertyChanged Event Handler

Jonas — Thu, 26 Jun 2008 20:11:00 GMT

You can use the new partial methods. LINQ to SQL uses them everywhere.

partial void OnUserIDChanging(int value);

partial void OnUserIDChanged();

public int UserID

{

get

{

return this._UserID;

}

set

{

if ((this._UserID != value))

{

this.OnUserIDChanging(value);

this.SendPropertyChanging();

this._UserID = value;

this.SendPropertyChanged("UserID");

this.OnUserIDChanged();

}

The SendPropertyChanging method raises the event just like you are doing.