Sent: Wednesday, 23 March 2011 12:59 PM
To: ozDotNet
Subject: RE: Raising property changed events
Apparently (according to Brendon Forster :)) All the cool kids are using this.
http://code.google.com/p/notifypropertyweaver/
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun
On Thu, Mar 24, 2011 at 4:42 PM, Stephen Price step...@littlevoices.com wrote:
Thanks David. I feel much happier about my rant now. I don't usually do
them, but really happy to know that it's not fallen on deaf ears.
Passing it up the chain is the best thing I could hope for, short of the
/system.runtime.compilerservices.methodimploptions.aspx
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Kean
Sent: Tuesday, March 22, 2011 10:06 PM
To: ozDotNet
Subject: RE: Raising property changed events
Hmm, I'll check internally, but I'd
/system.runtime.compilerservices.methodimploptions.aspx
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:
ozdotnet-boun...@ozdotnet.com] On Behalf Of David Kean
Sent: Tuesday, March 22, 2011 10:06 PM
To: ozDotNet
Subject: RE: Raising property changed events
Hmm
Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Mark Hurd
Sent: Thursday, March 24, 2011 5:20 PM
To: ozDotNet
Subject: Re: GetCurrentMethod possibly returning the wrong method (was Re:
Raising property changed events)
Thanks for that clarification
.
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Mark Hurd
Sent: Tuesday, March 22, 2011 9:36 PM
To: ozDotNet
Subject: Re: Raising property changed events
On 23 March 2011 15:00, Mark Hurd markeh...@gmail.com wrote:
I believe
-Original Message-
From: Stephen Price step...@littlevoices.com
Sender: ozdotnet-boun...@ozdotnet.com
Date: Wed, 23 Mar 2011 21:48:10
To: ozDotNetozdotnet@ozdotnet.com
Reply-To: ozDotNet ozdotnet@ozdotnet.com
Subject: Re: Raising property changed events
I was going to use
On 24 March 2011 00:54, djones...@gmail.com wrote:
snip
I haven't pressed F1 in visual studio since early 2001. It's a waste of
time installing the docs as google will give you better and more concise
information in half the time.
/snip
Couldn't agree more.
SQL Server documentation however
...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of djones...@gmail.com
Sent: Wednesday, March 23, 2011 6:54 AM
To: ozDotNet
Subject: Re: Raising property changed events
Imo. This has been the problem with msdn since the inception of .net.
The last usable msdn was '98. Where you could find
: Thursday, 24 March 2011 2:17 AM
To: djones...@gmail.com; ozDotNet
Subject: RE: Raising property changed events
If you come across pages where you think the docs need improvement, please
use the Rating box in the top right. Given that there's something like
200,000+ pages on MSDN, the UE (doc
*Subject:* RE: Raising property changed events
If you come across pages where you think the docs need improvement, please
use the Rating box in the top right. Given that there’s something like
200,000+ pages on MSDN, the UE (doc guys) combine that with page views to
focus on low rated, high
gives broader
information than MSDN does.
Cheers,
Trevor**
*From:* ozdotnet-boun...@ozdotnet.com [mailto:
ozdotnet-boun...@ozdotnet.com] *On Behalf Of *David Kean
*Sent:* Thursday, 24 March 2011 2:17 AM
*To:* djones...@gmail.com; ozDotNet
*Subject:* RE: Raising property changed events
...@ozdotnet.com] On
Behalf Of Stephen Price
Sent: Wednesday, March 23, 2011 7:26 PM
To: ozDotNet
Subject: Re: Raising property changed events
Assuming around 200 people on the list, if we each take 1000 pages we should be
able to tag them all with a please provide examples
I get what you
.
*From:* ozdotnet-boun...@ozdotnet.com [mailto:
ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Stephen Price
*Sent:* Wednesday, March 23, 2011 7:26 PM
*To:* ozDotNet
*Subject:* Re: Raising property changed events
Assuming around 200 people on the list, if we each take 1000 pages we
should
Raising property changed events seems like something that most applications
need to do at some stage. C#3 introduced the auto property i.e. public bool
IsBusy { get; set; }
I am surprised that there isn't a way built into the framework to
automatically raise changed events
Anyway, i saw
: Raising property changed events
Raising property changed events seems like something that most applications
need to do at some stage. C#3 introduced the auto property i.e. public bool
IsBusy { get; set; }
I am surprised that there isn't a way built into the framework to automatically
raise changed
: Wednesday, 23 March 2011 1:59 PM
To: ozDotNet
Subject: RE: Raising property changed events
Apparently (according to Brendon Forster :)) All the cool kids are using this.
http://code.google.com/p/notifypropertyweaver/
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com
:
Raising property changed events seems like something that most applications
need to do at some stage. C#3 introduced the auto property i.e. public bool
IsBusy { get; set; }
I am surprised that there isn't a way built into the framework to
automatically raise changed events
Anyway, i saw this code
:
Raising property changed events seems like something that most applications
need to do at some stage. C#3 introduced the auto property i.e. public bool
IsBusy { get; set; }
I am surprised that there isn't a way built into the framework to
automatically raise changed events
Anyway, i saw
Below is not guaranteed to work, if we inline the set, GetCurrentMethod will
return the wrong method.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Burela
Sent: Tuesday, March 22, 2011 7:57 PM
To: ozDotNet
Subject: Raising property changed events
, March 22, 2011 7:57 PM
To: ozDotNet
Subject: Raising property changed events
Raising property changed events seems like something that most applications
need to do at some stage. C#3 introduced the auto property i.e. public bool
IsBusy { get; set; }
I am surprised that there isn't a way
On 23 March 2011 15:00, Mark Hurd markeh...@gmail.com wrote:
I believe it was in this mailing list that we previously confirmed
using GetCurrentMethod, even when included in convoluted ways,
guarantees the method will not be inlined.
Gmail says GetCurrentMethod has /not/ been mentioned before
On Wed, Mar 23, 2011 at 3:30 PM, Mark Hurd markeh...@gmail.com wrote:
I believe it was in this mailing list that we previously confirmed
using GetCurrentMethod, even when included in convoluted ways,
guarantees the method will not be inlined.
Can you show an example where GetCurrentMethod
. In which case, if we don't give
the above guarantee I'll make sure they call it out.
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Mark Hurd
Sent: Tuesday, March 22, 2011 9:36 PM
To: ozDotNet
Subject: Re: Raising property
GetCurrentMethod is of little use to us netcf people since it doesn't
exist. In fact, I believe there is no way to get the method name in
netcf for a release build.
David
If we can hit that bullseye, the rest of the dominoes
will fall like a house of cards... checkmate!
-Zapp Brannigan,
25 matches
Mail list logo
