Commented Issue: Inconsistent Key Parameters with Actions [878]

I am using a guid for the key of my entity. When requesting the entity I must use a format like the following.

```
http://site/odata/MyEntities(062e803f-e61d-48c7-a65d-835ff232632f)
```

Using the OData format below fails.
```
http://site/odata/MyEntities(guid'062e803f-e61d-48c7-a65d-835ff232632f')
```

I also have an action on that entity and in order to call the action I must use the following format.
```
[POST]
http://site/odata/MyEntities(guid'062e803f-e61d-48c7-a65d-835ff232632f')/MyAction
```
as the below format fails.
```
[POST]
http://site/odata/MyEntities(062e803f-e61d-48c7-a65d-835ff232632f)/MyAction
```
This seems very odd and confusing its the same resource so they should be addressable the same way.

Adam
Comments: Ah yes, I had an override on my GET that didn't have that attribute on the parameter. When I remove the override of GET then I can call with the OData standard guid'xxxx'. Nice catch! Thanks, Adam