Eric De C#

nice post

2010-03-12T11:41:33.604-05:00

nice post

@Rick Someone posted the solution: http://blog.dec...

2010-02-23T10:35:25.005-05:00

@Rick
Someone posted the solution:
http://blog.decarufel.net/2009/07/how-to-use-inotifypropertychanged-type_22.html
Quote Stefan Lange:
Very good idea! After I tried it out I have two hints:

If the property is a value type you need an additional step to unbox the expression body:

((MemberExpression)((UnaryExpression)propertyExpression.Body).Operand).Member.Name

The only reason why you must compile and execute the expression is to retrieve the sender. I would avoid this completely by simply adding the sender to the parameters:

PropertyChanged.Raise(this, () => Data);

I think adding the sender is better than creating code to retrieve it.

Thanks, I was looking for this. Does anyone know ...

2010-02-12T14:19:16.311-05:00

Thanks, I was looking for this.

Does anyone know where to find all attributes that apply to PropertyGrid?

thanks for the great info. it will surely help me ...

2010-01-27T14:26:44.343-05:00

thanks for the great info. it will surely help me a lot
Cheers

Yes intellisense will ignore it but you will still...

2010-01-26T08:45:22.817-05:00

Yes intellisense will ignore it but you will still be able to use it anyway. The goal here is to make your code foul proof.

I would suggest another approach to do this, usual...

2010-01-26T08:41:28.172-05:00

I would suggest another approach to do this, usually the user if the member is not documented, nor visible to intellisense won't know about them.

Conviniently the framework includes the wollowing attribute so intellisense will ignore it:

System.ComponentModel.EditorBrowsableAttribute

Especifing System.ComponentModel.EditorBrowsableState.Never should make the trick!

[EditorBrowsable(EditorBrowsableState.Never)] public string[] Types { get; set; }

Thanks for posting this article. This is exactly w...

2010-01-08T10:49:39.702-05:00

Thanks for posting this article. This is exactly what I needed.
-swathi

I'm trying to implement this and one boolean prope...

2009-11-25T10:55:17.648-05:00

I'm trying to implement this and one boolean property is causing a property expression should be a member expression error. When I break on if (body -- null), body is null, but if I highlight propertyExpression.body in quick watch it returns the lambda... Very strage but prevents it from working. Any ideas?

Microsoft Visual Studio 2010 and .NET Framework 4 ...

2009-11-20T11:16:36.143-05:00

Microsoft Visual Studio 2010 and .NET Framework 4 Beta 2 enhance support for parallel programming with a new runtime, new class library types, and diagnostic tools. These features simplify parallel development and enable developers to write efficient, fine-grained, and scalable parallel code in a natural idiom without having to work directly with threads, or the thread pool. The following illustration provides a high-level overview of the parallel programming architecture in .NET Framework 4 Beta 2.

No you can't. For default XML serialization to wo...

2009-11-12T18:26:24.940-05:00

No you can't. For default XML serialization to work you must have a public default constructor. You can build your own XmlSerializer but it's a lot more work.

Another way to do that is to mark the parameterles...

2009-11-12T17:56:20.384-05:00

Another way to do that is to mark the parameterless constructor as private!

I think Kodu can be categorized as a serious fun D...

2009-11-12T07:23:57.916-05:00

I think Kodu can be categorized as a serious fun Download Games. It doesn't have realistic graphics, huge explosion, or even a way to win. But Kodu makes creating is more challenging than consuming. I think it's one of the best and creative games ever.

AccountDecorator has a few issues, firstly: all of...

2009-10-05T12:13:43.253-04:00

AccountDecorator has a few issues, firstly: all of the properties/methods refer to _account as Account which would be incorrect since that would be a static member to the Account class. I assume this was an oversight as you were typing up your blog post.

The more pressing issue is why does AccountDecorator exist at all? You could have easily have just used the original account since there was no purpose to your decoration of it. Or you could've created something like

IValidatorMember&ltT&gt class

and instead of AccountValidatorBase : AccountDecorator you would use

AccountValidatorBase : IValidatorMember&ltIAccount&gt

I think it's much more preferable for wrapper classes to be implemented through generics so you don't end up with double the amount of files per classes you have.

Great posting, well explained, practical and very ...

2009-10-03T08:49:00.459-04:00

Great posting, well explained, practical and very useful. Thanks!

Very insightful. I wish there was dedicated print ...

2009-10-03T04:18:09.037-04:00

Very insightful. I wish there was dedicated print option, with all images and source code properly laid out on page. Keep the good stuff coming!

This was a very timely and content rich post for m...

2009-10-02T10:17:18.465-04:00

This was a very timely and content rich post for me to read, Eric, thank you!

Very good idea! After I tried it out I have two hi...

2009-09-09T20:06:13.699-04:00

Very good idea! After I tried it out I have two hints:

If the property is a value type you need an additional step to unbox the expression body:

((MemberExpression)((UnaryExpression)propertyExpression.Body).Operand).Member.Name

The only reason why you must compile and execute the expression is to retrieve the sender. I would avoid this completely by simply adding the sender to the parameters:

PropertyChanged.Raise(this, () => Data);

I think adding the sender is better than creating code to retrieve it.

Sweeeet :p

2009-09-08T10:27:11.851-04:00

Sweeeet :p

Hi, great idea. I got inspired by that and wrote s...

2009-08-01T09:11:41.395-04:00

Hi, great idea.
I got inspired by that and wrote something about it.
Have a look at http://gfoidl.spaces.live.com/blog/cns!36D34E66505CE4AF!201.entry

Altought it's written in German language the code should be readable.
It's very little code needed and shows a variant with reflection where even no arguments are needed.

Maybe this can be improve to keep a cache but in m...

2009-07-23T13:44:27.265-04:00

Maybe this can be improve to keep a cache but in most enterprise application the cost is negligible.

Of course most refactoring tool will catch it, but what if someone change a property name without refactoring? It will compile but won't work.

This is a very neat trick, rename refactor will pr...

2009-07-23T13:31:11.555-04:00

This is a very neat trick, rename refactor will probably catch this as well?

I'm worried about the reflection cost in vmlambda.Compile(). Will caching work here?

See my next post to find a solution I think worth ...

2009-07-22T18:17:14.157-04:00

See my next post to find a solution I think worth trying.

Nope, because you can't raise the event from your ...

2009-07-22T10:58:39.325-04:00

Nope, because you can't raise the event from your extension method.

I think that you could just write the extension me...

2009-07-22T08:23:08.062-04:00

I think that you could just write the extension method for the INotifyPropertyChanged interface, then do:

"this.Raise(()=>Data)" and the inheritance problems go away.

You are right. You need PropertyChanged event defi...

2009-07-22T07:28:56.974-04:00

You are right. You need PropertyChanged event defined in every derived classes, but it it's not so good because they will "hide" the base implementation.

Another way to do this would be to define a virtual method on the base class that take a "Expression Of (Func Of object)" and use it to call the PropertyChanged event.

I used to implement my INPC interface like this:
#region INotifyPropertyChanged Members

private string[] GetPropertiesList()
{
Type t = GetType();
PropertyInfo[] properties =
t.GetProperties(BindingFlags.Instance | BindingFlags.Public | BindingFlags.SetProperty);

var propList = new string[properties.Length];
for (int i = 0; i < properties.Length; i++)
propList[i] = properties[i].Name;
return propList;
}

public void RaisePropertyChanged(params string[] properties)
{
if (properties.Length == 0)
properties = GetPropertiesList();

foreach (string property in properties)
OnPropertyChanged(new PropertyChangedEventArgs(property));
}

private void OnPropertyChanged(PropertyChangedEventArgs e)
{
if (PropertyChanged != null)
PropertyChanged(this, e);

OnPropertyChangedCore(e);
}

protected virtual void OnPropertyChangedCore(PropertyChangedEventArgs args) {}

public event PropertyChangedEventHandler PropertyChanged;

#endregion