Comments for Rob's Tech Blog

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Rob

Rob — Sat, 28 Jan 2012 15:51:42 +0000

Not as fast as this one

Comment on There’s a maximum of 255 local messaging channels in Silverlight 4 by Rob

Rob — Sat, 28 Jan 2012 15:50:22 +0000

100%

Comment on Slides from my Apps World talk: Beginning Windows Phone 7 Development by WINDOWS PHONE 7 DEVELOPMENT

WINDOWS PHONE 7 DEVELOPMENT — Fri, 23 Dec 2011 06:41:41 +0000

Nice post.Thanks For Sharing.Its Nice to have WP7 is primarily focused on the consumer market rather than the enterprise market. Incorporated with its unique tiles based User Interface (UI), WINDOWS PHONE 7 DEVELOPMENT moves a step ahead from traditional concept of icons. "

Comment on There’s a maximum of 255 local messaging channels in Silverlight 4 by Amish

Amish — Fri, 09 Dec 2011 06:29:48 +0000

Are you sure about the number of channels ?

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Tom

Tom — Tue, 18 Oct 2011 19:41:23 +0000

You can find a high performance solution to raise property changes without magic strings here: http://tomsundev.wordpress.com/category/articles/update-property-change-notification-without-strings/

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Rob

Rob — Thu, 06 Oct 2011 09:42:44 +0000

“nameof” is exactly what i was hoping would be added to C# in order to solve this (although it would be a more general solution if you got a System.Reflection.MemberInfo back – to closer match typeof()).

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Christoph

Christoph — Thu, 06 Oct 2011 07:57:15 +0000

That is why I always thought a “nameof()” operator would be an awesome addition to the language (as proposed here http://codefluff.blogspot.com/2010/05/case-for-nameof-operator.html ) to get rid of all the magic strings. At least now there will be a few less of them in c#5.

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Rob

Rob — Wed, 05 Oct 2011 23:35:51 +0000

Oh sure I see. We have a rule on our project: INPC is only for WPF’s benefit. If your code needs to depend on a property changing, then we implement a plain event specifically for that property…

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Caleb Vear

Caleb Vear — Wed, 05 Oct 2011 23:33:11 +0000

You can just use NotifyPropertyWeaver now and you don’t even need to implement the properties, just use auto properties.

http://code.google.com/p/notifypropertyweaver/

Comment on Raising the right PropertyChanged with C# 5′s Caller Info Attributes by Andy Lowry

Andy Lowry — Wed, 05 Oct 2011 18:53:30 +0000

Hi Rob, unless your binding using WPF or some other library that handles the dirty work for you. The client of your INotifyPropertyChanged class needs to handle the PropertyChanged event and then use the string name to determine which property has changed. This still has the same problems as before.

I think INotifyPropertyChanged is the problem. It would be nice to replace it with something easier to use.