Re:Why .NET?
by manigandham on Tuesday December 15, 2015 @12:26AM
(#10736108)
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
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.
Re:Why .NET?
by manigandham on Thursday December 17, 2015 @01:33AM
(#10749968)
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.
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.