Concurrency mode: optimistic auto generated Timestamp property

[dcastenholz]

2 separate, yet related bugs:

1. When Concurrency is set to optimistic, and no property is marked as "Is Concurrency Token", the extension automatically creates a working Timestamp property, but the extension throws an error saying: "Entity1: Should have 1 concurrency properties but has 0".

2. If you add a property and then mark it as "Is Concurrency Token" = True, the generated property has [Required] on it which causes validation errors on save. The UI does not allow you to change the Required = True setting.

[dcastenholz]

Not trying to complicate things, but maybe Timestamp and ConcurrencyCheck should be separated. The auto-generated Timestamp works well other than the extraneous error that is generated by the extension. Build and functionality are both fine. Workaround is to just ignore the error.

[msawczyn]

That'll be fixed in the next version. Thanks for pointing it out.

[msawczyn]

This was a tricky one, philosophically, to deal with. In the best of all worlds, the designer and the code generation are separate. Yet the designer should know that the concurrency property will be automatically generated and not give the error. While not the best of all solutions, I've removed the error message, and that change is available in v1.2.6.18.

[msawczyn]

Closing since fix is now released