/// <summary>
/// This is a re-implementation of MvcContrib.FluentHtml.Behaviors.MemberBehaviorHelper{T}
/// that is aware of MetadataTypeAttribute from DataAnnotations.
/// </summary>
internal static class AnnotationsHelper
{
// Methods
public static T GetAttribute<T>(IMemberElement element) where T : Attribute
{
return GetAttribute<T>(element.ForMember);
}

public static T GetAttribute<T>(MemberExpression expression) where T : Attribute
{
if (expression == null)
return default(T);

var metadataAttrib = expression.Member.DeclaringType
.GetCustomAttributes(typeof(MetadataTypeAttribute), true)
.Cast<MetadataTypeAttribute>().FirstOrDefault();

if (metadataAttrib == null)
{
return expression.Member.GetCustomAttributes(typeof(T), true)
.Cast<T>().FirstOrDefault();
}

return (from prop in TypeDescriptor.GetProperties(metadataAttrib.MetadataClassType).Cast<PropertyDescriptor>()
where prop.Name == expression.Member.Name
select prop.Attributes.OfType<T>().FirstOrDefault()).FirstOrDefault();
}

public static MethodInfo GetMethod(IMemberElement element, string methodName)
{
return element.ForMember == null ? null : element.GetType().GetMethod(methodName);
}

public static void InvokeMethod(MethodInfo method, IMemberElement element, params object[] parameters)
{
method.Invoke(element, parameters);
}
}

When using a proxy generated by svcutils ?

I’ve tried to use a code to replace the behaviour in the client – but it doesn’t work (the deserializer looking from staff in the wrong places… – looking for on of my server entities in mscorlib) :
foreach (OperationDescription desc in this.Endpoint.Contract.Operations)
{
DataContractSerializerOperationBehavior dcsOperationBehavior = desc.Behaviors.Find();
if (dcsOperationBehavior != null)
{
int idx = desc.Behaviors.IndexOf(dcsOperationBehavior);
desc.Behaviors.Remove(dcsOperationBehavior);
desc.Behaviors.Insert(idx, new NetDataContractOperationBehavior(desc));

}
}

Is there anyone who learnt anything new reading that article by Joel and/or those countless replies?

var clientIds = {
firstName: ‘# x.User.FirstName)%>’
};

Then later your actual jQuery code is much cleaner:

$(clientIds.firstName).change(doSomething);

Parenthesis are optional in VB – some interesting kind of bugs might appear because of this.

But benefit is crucial.

If parens were optional on methods with no params in C#, this trouble would disappear.