https://github.com/supendi/adository
An ADO .Net repository generator for C# and Visual Basic
https://github.com/supendi/adository
ado-dotnet ado-net dal-generator data-access-layer data-access-layer-generator repository-generator
Last synced: about 1 month ago
JSON representation
An ADO .Net repository generator for C# and Visual Basic
- Host: GitHub
- URL: https://github.com/supendi/adository
- Owner: supendi
- Created: 2019-02-05T03:05:28.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-02-05T10:17:38.000Z (over 6 years ago)
- Last Synced: 2025-03-26T01:41:26.590Z (about 2 months ago)
- Topics: ado-dotnet, ado-net, dal-generator, data-access-layer, data-access-layer-generator, repository-generator
- Language: C#
- Size: 4.21 MB
- Stars: 5
- Watchers: 1
- Forks: 4
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Adository
What it Adository?
If you are a fans of ADO .Net and want to stick with it because you dont want to migrate to EF yet, then here is a tool for you to generate repository classes using ADO .Net. Or in other word it is a data access layer generator tool
Supported Language and Database
Database: SQL Server
Language: C# and Visual Basic
How To Generate Repository Classes
It's recommended to create a separated project (class library) to put the generated code.
1. Open The App (Build/Run the project)
2. Pick Language (C# or VB)
3. Login using sql server password or windows
4. Select a database node and click 'Generate Repository' Context Menu
5. Type your namespace name, DbContext name, and select a folder project where you want to generate the files.
6. In your IDE (visual studio) point to project where the files generated. Show all files, select the generated folders and files then include to your project
7. Note that the dbcontext class will read connection string from config file(app.config or web.config). So you must add/create your own connection string in the config file
Use the generated code
It's a bit similiar to how we use an EF dbcontext object.