3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Johnathan Miles commented  ·  October 2, 2012 1:31 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is available already as a pre-release here:

  http://blogs.msdn.com/b/astoriateam/archive/2012/07/02/trying-out-the-prerelease-odata-client-t4-template.aspx

  You can quite easily modify this template to do what you wish with the client generated code.

• Kevin Logan commented  ·  September 19, 2011 8:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Mainly I'd like to add a check for if the value has changed, then don't fire the propertyChanged event. See http://stackoverflow.com/questions/7432540/can-i-change-the-t4-for-a-silverlight-wcf-data-service-servicereference.

• Robert McLaws commented  ·  September 10, 2010 11:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I 100% agree, it should be far easier to share types than it is now. I think the default client generator should be replaced with Self-Tracking Entities... there is no need to duplicate functionality when STEs are clearly more feature-complete.