1) This was indeed an issue with the Model Settings dialog which has been fixed in the latest internal build (version 2010.3.1306).
2) I am afraid that the naming settings are applied only to new classes. Currently there is no way to "refresh" the existing classes as this would break your code, if you are already using the classes.
3) The field rules are applied to the private fields of the generated classes while the property rules are applied to the public properties which expose the private fields. There are cases when the field and properties should have different names (for example in VB.Net) and this allows to set the naming rules separately.
4) Yes, this would be detected as a difference because the schema read from the database and the one available in your domain model have different information about this column. You should not normally need to set a column as primary key, the only thing you need to do in order to use views is to enable the Identity
setting for one or more of the properties of the meta class.
5) If your database contains multiple schemas, we are reading only their names and when you choose the ones to update from, their full definition is read. I am afraid that there is not much that can be optimized in this process.
6) With the last Q3 release we introduced a new type conversion framework which allows to define custom type converters. I think you will be able to use such custom converter to map number columns to Int32 fields but this would require some code to be written additionally to your domain model. Please let me know if this would work for you, so I can provide you with more details.
I hope that helps.
the Telerik team