Originally posted by DimPrawn
View Post
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Reply to: Is .NET Entity Framework still cool?
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Is .NET Entity Framework still cool?"
Collapse
-
-
Originally posted by woohoo View PostNever found it an issue with embedded sql, you tend to organise the repositories so they make sense. 80% of your work is simple update/insert/delete/fetch and you can use contrib so this basic sql is done for you.
It's one of those if you can write decent sql and can organise a piss up in brewery you can successfully use Dapper or most other micro-orms.
Dapper does have it's limitations, same for repository pattern but this crap about magic strings is nonsense.
I'm not slating Dapper, I've used it and I like it, was just pointing out to +/- points to consider.
Leave a comment:
-
Originally posted by woohoo View PostNever found it an issue with embedded sql, you tend to organise the repositories so they make sense. 80% of your work is simple update/insert/delete/fetch and you can use contrib so this basic sql is done for you.
It's one of those if you can write decent sql and can organise a piss up in brewery you can successfully use Dapper or most other micro-orms.
Dapper does have it's limitations, same for repository pattern but this crap about magic strings is nonsense.
Leave a comment:
-
Originally posted by DimPrawn View PostTotally different in that this works with a whole bunch of databases (the MS Linq to SQL only worked with MS SQL Server).
But is of the same philosophy in that it provides Linq to database SQL generation. Unlike Dapper where you end up with embedded SQL strings all over the place.
It's one of those if you can write decent sql and can organise a piss up in brewery you can successfully use Dapper or most other micro-orms.
Dapper does have it's limitations, same for repository pattern but this crap about magic strings is nonsense.
Leave a comment:
-
Originally posted by d000hg View PostIs that the old LINQ MS did for DB, then backtracked on when LINQ was new and cool, or totally different?
Sent from my ONEPLUS A6003 using Tapatalk
But is of the same philosophy in that it provides Linq to database SQL generation. Unlike Dapper where you end up with embedded SQL strings all over the place.
Leave a comment:
-
Originally posted by DimPrawn View PostAnother alternative, slightly above Dapper (no magic strings), but less heavyweight than EF (no object state tracking).
Supports lots of different databases, including SQL Server, Oracle, SQLite, DB2, MySql etc
GitHub - linq2db/linq2db: Linq to database provider.
Sent from my ONEPLUS A6003 using Tapatalk
Leave a comment:
-
Another alternative, slightly above Dapper (no magic strings), but less heavyweight than EF (no object state tracking).
Supports lots of different databases, including SQL Server, Oracle, SQLite, DB2, MySql etc
GitHub - linq2db/linq2db: Linq to database provider.
Leave a comment:
-
I use EF for one of the systems that I sell commercially. It's a bit heavyweight for my needs and to be honest, I wish I had gone with Dapper instead but I'm way too lazy to refactor it and it works, so...
Check out Dapper first - it does what the majority of people need quite nicely, and it's much more lightweight than EF.
Never used nHibernate. I use hibernate for java projects, but not for .NET. No idea why actually.
Leave a comment:
-
Originally posted by d000hg View PostI seem to go through periods of using C# actively every couple of years. Typically that means that while the language may have moved on a bit, a whole new database access framework has become de rigueur.
I think last time I was quite keen on EF but has it since fallen from favour? My DB needs are quite modest, by main query is whether to wrap all DB access in stored procedures as was deemed best practice at times, or just use EF which (sort of) achieves the same goal.
What do you C# monkeys do these days for standard SQL DB access, those of you who haven't all moved to Big Data and NoSQL gravy trains at least? My use case is predominantly to store received data from a 3rd party.
I tend to use a micro-orm called Dapper, it meets all my needs, simple and fast. You can use it with stored procs if you want but I tend to use inline sql along with Dapper.Contrib which makes it even easier. For example
var id = await cn.InsertAsync(customer);
Get it here.
GitHub - StackExchange/Dapper: Dapper - a simple object mapper for .Net
For what it's worth, I tend to stick with a repository pattern (has it's faults) but it's simple. I like simple.
Leave a comment:
-
Is .NET Entity Framework still cool?
I seem to go through periods of using C# actively every couple of years. Typically that means that while the language may have moved on a bit, a whole new database access framework has become de rigueur.
I think last time I was quite keen on EF but has it since fallen from favour? My DB needs are quite modest, by main query is whether to wrap all DB access in stored procedures as was deemed best practice at times, or just use EF which (sort of) achieves the same goal.
What do you C# monkeys do these days for standard SQL DB access, those of you who haven't all moved to Big Data and NoSQL gravy trains at least? My use case is predominantly to store received data from a 3rd party.Tags: None
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Leave a comment: