Entity CodeFirst EF6, EntityData string id

Question

Have started to use Entity Code First with Azure Mobile Services and have met some issue:

For using TableController with Entity objects I need to derive each of them from EntityData class, that provide string Id field!

I used to use int, long and even guid instead string for id, so...

What is benefits of this? What about insert operation and what is the best practice for this? What about performance for string id?

Answer 1

@carlosfigueira has a good writeup about the change to using string id here: http://blogs.msdn.com/b/carlosfigueira/archive/2013/11/23/new-tables-in-azure-mobile-services-string-id-system-properties-and-optimistic-concurrency.aspx