Thank you for your suggestion.
I would like to point out the behaviour of the wizard when "Use the project namespace"
option is selected is correct. Your suggestion about the format of the entity type full name when DB Schema name is considered is very useful and convenient. For time being the full name in that case will be <SCHEMA NAME>.<ENTITY NAME>.
You can enable this name generation pattern by checking "Use schema names for namespaces"
checkbox on "Choose Database Items"
step of the wizard. Keep in mind that the default "dbo"
schema is treated as empty string and the wizard will use the project namespace instead
We are considering your request for implementation, but due to the fact that there could be production code using the existing naming approach we will need additional time to decide on the best way to introduce the new naming convention. This means we most like will not be able to implement your request for the incoming release in the beginning of June.
Meanwhile you can use OpenAccess Batch Operations tool for mass rename/change of namespace of your types. You can find more information about this tool in our online documentation
In order to do that you can:
- Open your RLINQ file;
- Right click on the design surface and select Batch Operations... from the context menu
- Select from Operations combobox in the right panel : Change Namespace
- Enter the new namespace
- Select one or many entity row from the grid as targets of the operation
- Press Execute button
- Save the RLINQ file and rebuild your solution
If you would like to add any details about your feature request, have another suggestion or need assistance do not hesitate to contact us.
the Telerik team
Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!