hris Walsh
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:ozd
n.methodattributes
-Original 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:
Rais
ions. 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, Mar
riginal 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'
brary/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,
On Thu, Mar 24, 2011 at 4:42 PM, Stephen Price 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
> documentation actually be
can’t directly impact the docs as a whole (other adding comments
> to them where I can, and making sure my feature’s docs are good) – I will
> forward this thread onto a couple of people who can impact them.
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun
o a couple of people who can impact them.
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
n 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 viewed pages first.
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *djones...@gmail.com
> *
..@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
>
>
>
> If you come across pages where you think the docs need improvement, please
> use the Rating box i
Kean
Sent: 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 MS
-boun...@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
On 24 March 2011 00:54, wrote:
> 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.
Couldn't agree more.
SQL Server documentation however is and always has been exc
h
the same way about xml
-Original Message-
From: Stephen Price
Sender: ozdotnet-boun...@ozdotnet.com
Date: Wed, 23 Mar 2011 21:48:10
To: ozDotNet
Reply-To: ozDotNet
Subject: Re: Raising property changed events
I was going to use this an opportunity to vent about the msdn documentation
e, 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
> Subjec
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, Futu
tly in certain situations. 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: ozD
On Wed, Mar 23, 2011 at 3:30 PM, Mark Hurd 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 does not return th
On 23 March 2011 15:00, Mark Hurd 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 this
mailing l
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 does not return the
expected method?
--
Regards,
Mark Hurd, B.Sc.(Ma.)(Hons.)
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
Caliburn.Micro uses Expressions
public virtual void NotifyOfPropertyChange(string propertyName) {
if(IsNotifying)
Execute.OnUIThread(() =>
RaisePropertyChangedEventCore(propertyName));
}
public virtual void
NotifyOfPropertyChange(Expression>
pro
Yeah, it's so damn annoying to have to expand an auto property to do
raised events, but in some cases you need to, most of the time for
RaisePropertyChanges I'd opt to use a extension/helper method that
accepts a lambda:
RaisePropertyChange(()=> this.PropertyName);
But I'd only use that in instan
1 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] On
Behalf Of David Burel
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] On
Behalf Of David Burela
Sent: Wednesday, 23 March 2011 1:57 PM
To: ozDotNet
Subject: Raisin
25 matches
Mail list logo
