When adding a key value to the controller context RouteValues, the value should be coerced into the appropriate CLR type based upon the Key of the EntitySet in question. The lack of this causes an issue with Guids since the "guid''" wrapper around the value is kept and sent along as a string.
Comments: OK, I will give it a shot. I was a bit confused by the fact binding via a string doesn't require the attribute and that some examples I've seen use integer based keys as well without the attribute.
Comments: OK, I will give it a shot. I was a bit confused by the fact binding via a string doesn't require the attribute and that some examples I've seen use integer based keys as well without the attribute.