Announcing .NET Core 1.0

Re:Announcing .NET Core 1.0 by jsingleton on Monday June 27, 2016 @12:11PM (#11987120)

I would be surprised if there wasn't a free (as in beer) Express version for Linux, with a DB size limit like 10GB. Otherwise Entity Framework Core supports PostgreSQL, but there isn't any lazy loading yet.

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by chrshawkes on Monday June 27, 2016 @01:27PM (#11987742)

I don't believe it works outside of using EF. Last I checked no database drivers existed for .NET Core for MySQL and PostgreSQL. For that reason I've stuck to Django.

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by manigandham on Monday June 27, 2016 @01:33PM (#11987798)

npgsql is the open-source default driver for PostgreSQL and works with .NET core (netstandard 1.3):

https://github.com/npgsql/npgsql

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by jsingleton on Monday June 27, 2016 @01:33PM (#11987796)

I believe you can use PostgreSQL with Dapper, as there is an ADO provider for PG, but I haven't tried this.

https://github.com/StackExchange/dapper-dot-net#will-dapper-...

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by AndreyErmakov on Monday June 27, 2016 @12:25PM (#11987226)

What I meant was that's just not enough. You can toy with it in a hobby project but in production that will be exhausted pretty soon.

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by eropple on Monday June 27, 2016 @01:27PM (#11987740)

I think that probably depends pretty heavily on what your app is. One of my clients has about 200,000 user accounts (and 40K actives/week) in a database that's well under 4GB, and it's been live for three years now. It's in Postgres, but there's nothing that'd stop them from using a 10GB-capped SQL Server Express until a point where having to pay for SQL Server is a good-problem-to-have.

[ Parent | on HN ]