Comments for On developing Pochet.NET

Comment on Synchronizing group row headers with column headers in Silverlight DataGrid by Emiel

Emiel — Fri, 23 Mar 2012 07:34:53 +0000

Please have a look at http://msdn.microsoft.com/en-us/library/dd833072%28VS.95%29.aspx

Comment on Synchronizing group row headers with column headers in Silverlight DataGrid by Eudson Bambo

Eudson Bambo — Wed, 21 Mar 2012 07:56:47 +0000

Good post,

I´ve been looking for this solution but when i implement that in my code i can manage the description but the data is not grouped.I do this in my code:
myGrid.GroupDescriptions.Add(GetColumnCaption(myGrid,columnName))

im stuck,,, some help

Comment on INotifyPropertyChanged implementations: An Overview by ibratoev

ibratoev — Wed, 07 Dec 2011 10:19:40 +0000

And BTW, simply caching the invocation expression will result in 10 time performance improvement (measured without the Math operation in the event handler).
Example:

private Expression useExpressionPropertyChanged;

public string UseExpression
{
get
{
return this.useExpression;
}
set
{
this.useExpression = value;

if (useExpressionPropertyChanged == null)
{
useExpressionPropertyChanged = () => UseExpression;
}

this.OnPropertyChanged(useExpressionPropertyChanged);
}
}

Comment on INotifyPropertyChanged implementations: An Overview by ibratoev

ibratoev — Wed, 07 Dec 2011 09:51:02 +0000

Nice post
Also consider using System.Diagnostics.Stopwatch. Results are a bit more precise. On my machine:
1 times using UseString => 299 ticks
1 times using UseStringVerified => 297 ticks
1 times using UseMethodBase => 305 ticks
1 times using UseMethodBaseVerified => 311 ticks
1 times using UseExpression => 384 ticks
1 times using UseExpressionVerified => 325 ticks
1 times using UseStackTrace => 352 ticks
1 times using UseStackTraceVerified => 339 ticks

501 times using UseString => 150202 ticks
501 times using UseStringVerified => 148810 ticks
501 times using UseMethodBase => 150633 ticks
501 times using UseMethodBaseVerified => 154308 ticks
501 times using UseExpression => 156054 ticks
501 times using UseExpressionVerified => 154616 ticks
501 times using UseStackTrace => 161979 ticks
501 times using UseStackTraceVerified => 164815 ticks

1001 times using UseString => 293697 ticks
1001 times using UseStringVerified => 294834 ticks
1001 times using UseMethodBase => 301462 ticks
1001 times using UseMethodBaseVerified => 305095 ticks
1001 times using UseExpression => 307167 ticks
1001 times using UseExpressionVerified => 306694 ticks
1001 times using UseStackTrace => 323592 ticks
1001 times using UseStackTraceVerified => 325578 ticks

1501 times using UseString => 442076 ticks
1501 times using UseStringVerified => 445532 ticks
1501 times using UseMethodBase => 448154 ticks
1501 times using UseMethodBaseVerified => 455503 ticks
1501 times using UseExpression => 461096 ticks
1501 times using UseExpressionVerified => 459862 ticks
1501 times using UseStackTrace => 490830 ticks
1501 times using UseStackTraceVerified => 488677 ticks

2001 times using UseString => 589203 ticks
2001 times using UseStringVerified => 593140 ticks
2001 times using UseMethodBase => 605011 ticks
2001 times using UseMethodBaseVerified => 606303 ticks
2001 times using UseExpression => 614216 ticks
2001 times using UseExpressionVerified => 615003 ticks
2001 times using UseStackTrace => 654534 ticks
2001 times using UseStackTraceVerified => 648982 ticks

Comment on Memory Leak in PanelDragDropTarget by Emiel

Emiel — Thu, 03 Nov 2011 09:19:50 +0000

trenttrobler has posted a solution here.

Comment on INotifyPropertyChanged implementations: An Overview by Sergey

Sergey — Fri, 28 Oct 2011 07:09:43 +0000

The Speed test is not correct. It performs 4000 System.Math operations in a PropertyChanged handler which dwarfs any speed differences in the methods tested. With an empty handler, this yields:

100000 times using UseString => 5.0003 ms
100000 times using UseStringVerified => 37.0021 ms
100000 times using UseMethodBase => 258.0148 ms
100000 times using UseMethodBaseVerified => 344.0197 ms
100000 times using UseExpression => 629.036 ms
100000 times using UseExpressionVerified => 629.0359 ms
100000 times using UseStackTrace => 1803.1031 ms
100000 times using UseStackTraceVerified => 1931.1105 ms

There is also CallerMemberName attribute in the upcoming C# 5 which tells the compiler to put the caller member name in the string parameter on which it is applied.

Comment on Silverlight DataContext Changed Event and Trigger by Eric

Eric — Fri, 16 Sep 2011 15:59:26 +0000

Thanks for this post. Exactly what I needed.

Comment on INotifyPropertyChanged: automatic dependent property and nested object support by Pasi

Pasi — Thu, 12 May 2011 13:04:08 +0000

Any news on how to make it work in a multi-threaded scenario?

Comment on Silverlight DataContext Changed Event and Trigger by Jason Rosenthal

Jason Rosenthal — Wed, 13 Apr 2011 19:51:41 +0000

Best solution to this problem I’ve seen! So I’ve converted it to vb.

Comment on INotifyPropertyChanged implementations: An Overview by nRoute – MVVM basics at John's technical weblog

nRoute – MVVM basics at John's technical weblog — Sun, 03 Apr 2011 15:51:37 +0000

[...] http://www.pochet.net/blog/2010/06/25/inotifypropertychanged-implementations-an-overview/. [...]