In general OpenAccess ORM will be used in both your Entity Layer and as a Data Access layer. In fact, you can just merge those two layers in one project. OpenAccess can be integrated as a code generation solution so that you can define your classes in the Visual Designer or as Code-Only Fluent Mapping. OpenAccess will also generate for you an OpenAccessContext which will be used for any activities concerning the database (CRUD operations, stored procedure calls, etc.).
The best practice in your case is to add a Telerik OpenAccess Class Library to your solution. It will run the OpenAccess New Domain Model wizard that will guide you through the setup of the .rlinq file. Since you have already created your database, you can use the detailed description here to navigate within that process.
The OpenAccess New Domain Model wizard, however, won’t add references to the OpenAccessModel project in the other assemblies in your solution (if any already). You have to do this manually following these steps:
1) Go to the project that will use the model
2) Add a reference to the model project in it
3) Add references to Telerik.OpenAccess.dll and Telerik.OpenAccess.35.Extensions.dll too
4) Copy the connection string from the App.config file of the model project to the corresponding place in the configuration file of the project that will use it (if that project doesn’t contain a *.config file, copy the App.config file from the model project and paste it in it)
More details about that process are available here.
You can also check the Quick – Start Scenarios folder in our documentation to get a better overview on how to combine Telerik OpenAccess ORM with the different .Net User Interface Platforms.
Do not hesitate to get back to us if you have additional questions.
All the best,
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!