Re: Lots of bind/notify classes

light.com] On Behalf Of Steven Nagy Sent: Friday, 28 May 2010 4:25 PM To: ozSilverlight Subject: RE: Lots of bind/notify classes Check out Post#: http://www.sharpcrafters.com/postsharp/documentation/getting-started Example: http://ruskin-dantra.blogspot.com/2009/03/inotifypropertychange

Re: Lots of bind/notify classes

M: +61 404 044 513 | E: steven.n...@readify.net | B: azure.snagy.name > > > > *From:* ozsilverlight-boun...@ozsilverlight.com [mailto: > ozsilverlight-boun...@ozsilverlight.com] *On Behalf Of *Steven Nagy > *Sent:* Friday, 28 May 2010 4:25 PM > *To:* ozSilverlight > *Subject:* RE

Re: Lots of bind/notify classes

M: +61 404 044 513 | E: steven.n...@readify.net | B: azure.snagy.name > > > > *From:* ozsilverlight-boun...@ozsilverlight.com [mailto: > ozsilverlight-boun...@ozsilverlight.com] *On Behalf Of *Steven Nagy > *Sent:* Friday, 28 May 2010 4:25 PM > *To:* ozSilverlight > *Subject:* RE

RE: Lots of bind/notify classes

Chaps, I have decided that snippets are the quickest way out of this at the moment. It doesn't modularise or reduce the property code, but at least it means I can create them faster. Actually, I forgot how good snippets are. For some reason I neglected them for the last couple of years, now I'm

Re: Lots of bind/notify classes

I just saw everyone was alredy talking about PostSharp. Sorry I should read the thread before replying. BTW, it doesn't affect Blendability. I can live with what Steven suggested, of having that extra line bit of code for each property, but it gets a bit messy when you have derived properties. O

Re: Lots of bind/notify classes

For the VMs I'm using an AOP (using CastleDynamicProxy for Debug and PostSharp for Release) to automatically do this for me. Jonas bloggedabout this approach. For PostSharp, I don't have a link, but I could send you a code that

RE: Lots of bind/notify classes

Friday, 28 May 2010 4:25 PM To: ozSilverlight Subject: RE: Lots of bind/notify classes Check out Post#: http://www.sharpcrafters.com/postsharp/documentation/getting-started Example: http://ruskin-dantra.blogspot.com/2009/03/inotifypropertychanged-made-easier.html Not sure if this works in Silve

RE: Lots of bind/notify classes

E: carl.scarl...@bankwest.com.au From: ozsilverlight-boun...@ozsilverlight.com [mailto:ozsilverlight-boun...@ozsilverlight.com] On Behalf Of Richard Mason Sent: Friday, 28 May 2010 2:22 PM To: ozSilverlight Subject: Re: Lots of bind/notify classes Hi Greg, I hear your pain and reflect it

RE: Lots of bind/notify classes

: steven.n...@readify.net | B: azure.snagy.name<http://azure.snagy.name/> From: ozsilverlight-boun...@ozsilverlight.com [mailto:ozsilverlight-boun...@ozsilverlight.com] On Behalf Of Greg Keogh Sent: Friday, 28 May 2010 4:18 PM To: 'ozSilverlight' Subject: Lots of bind/notify classes Look

Re: Lots of bind/notify classes

Hi Greg, I hear your pain and reflect it. You could probably set up a method using PostSharp to automatically create the necessary setter code, but that's provided you can introduce PostSharp into your process. The best I've managed is to set up a Visual Studio code snippet to help create them q

Lots of bind/notify classes

Look Dave, I can see you're really upset about this. I honestly think you ought to sit down calmly, take a stress pill, and think things over - HAL (2001) I was wondering if anyone has found a nice way of creating/managing lots of classes that are suitable for binding and implement INotifyPrope