[manigandham]

EF6 is still the recommended ORM and amazing at what it does. EF7 is still missing major features like Lazy-Loading so while you can use it in production, the team has repeatedly said that it's not recommended or necessary unless you have a specific reason to use it. Summer 2016 is when EF7 is supposed to be at full release.

EntityFramework can also support any underlying database and EF6 has providers for sql server, mysql, postgre, oracle, sqlite and many others. EF7 will even support nosql options like MongoDB.

What exactly is the issue with disk space for a published running app? The GAC (global assembly cache) in Windows was originally designed just for this: to share references and avoid having multiple copies of the same binaries. All this led to was a complicated situation with maintenance and reference nightmares. Disk space is exceedingly cheap and a strange to worry about when picking a tech stack.

[manigandham]

You can read more about EF7 RC1 here: http://blogs.msdn.com/b/dotnet/archive/2015/11/18/entity-fra...

They currently have working providers for SQL server, SQLite, SQL Server Compact, and PostgreSQL

[Ryuuke]

Great ! looking forward to see the changes in RTM version.

When I was talking about disk space I was referring to linux operating system where there is no GAC.

[manigandham]

Well there's no other way around it - you can either publish all the dependencies with each project or share them in a central place.

Central places don't work very well and again, file space is very cheap. Most binaries compress down very small so there really shouldn't be a disk space issue. And you can always remove dependencies if necessary.

It's just not something that has ever been a problem in over a decade of building and publishing .NET apps.

[Ryuuke]

yeah, you're probably right !