Hi,
Say we have a live mobile version which use a class like the following:

public class Example{

	[Key(0)]
	public int Field1 {get;set;}

	[Key(1)]
	public int Field2 { get; set}; 

}

Later on, the app no longer uses Field1, however Field1 property still wasn't removed from the class.

The question is, can we remove Field1 from the server code, in the future without break backward compatibility? (Remember that the apps not using Field1 in code, but Field1 exists in the Example class).

From tests we did, it seems like removing Field1 will break the backward compatibility and Example class won't succeed to be de-serialized.
Are we missing something?

Can we avoid such scenarios or are we "stuck" with such properties forever? (well until we enforce app updates with the property removal).

Thanks,
Tomer