I am sorry for both the misleading information in the referred forum thread, and the confusion you experienced.
Let me confirm that the feature is functional
, the tutorial in the documentation is correct
, and that the settings you applied
(according to the description in the referred forum thread) are correct
The behaviour you observe usually happens when an application is started without explicitly saving the domain model (the .rlinq file) first. On the Data Access side, saving the model is necessary, because it triggers our code generation functionalities, and they take care to preserve the new settings. In this connection, I suggest to you the following:
1. Open the .rlinq file in Visual Designer.
2. Move a class from one place to another on the diagram (in order to make a dummy change).
3. When the asterisk sign (*) next to the name of the model appears, save the model.
4. Run your application for a test.
I hope this helps. Do let us know about the outcome on your side, after applying the suggested workflow.
I am looking forward to your feedback.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map