Live data from Hacker News

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

31–40 of 327 posts

Re: Announcing .NET Core 1.0

#31

A bit unrelated, but I'm hoping to hear something soon about the future licensing model for the upcoming SQL Server on Linux. Do we get a free version without DB size / CPU / RAM limitations (but perhaps with some other restrictions) that smaller companies and startups can use in production? I'm planning to run my future ASP.NET MVC projects on Linux and very much would like to know if a better SQL Server Express / C…

Microsoft already announced the SQL Server on Linux licensing:

https://blogs.technet.microsoft.com/dataplatforminsider/2016...

"A customer who buys a SQL Server license (per-server or per-core) will be able to use it on Windows Server or Linux. This is just part of how we are enabling greater customer choice and meeting customers where they are."

Same editions, same prices.

Re: Announcing .NET Core 1.0

#32

Interesting name choice considering they have already had a .Net 1.0. I mean I get it, I understand why they chose to make this more of a 1.0 release but for those already in the .Net ecosystem it seems a little confusing to me.

Excuse me if this was already obvious, but the word "core" designates a new product line, starting from 1.0. Obviously, it's informed heavily from the old .net framework, but it's not backwards compatible with it.

Re: Announcing .NET Core 1.0

#33

A couple months ago I installed .NET core on a Ubuntu virtual machine running on the Windows 10 hypervisor, and was able to get a MVC5 app running using Visual Studio Code. As someone who really loves Visual Studio (it made me expect a lot more from my tools) and C# (it made me expect a lot more from my languages), it was an exciting moment. I actually took a selfie with my monitor. It was still a little rough: the "…

MVC 6 is the version that works best with Core, although they don't really refer to it directly much any more. Both MVC 6 and Web API 2 are now part of Core. They're just packages like everything else.

Re: Announcing .NET Core 1.0

#35

Earlier quoted context omitted.

I still can't shake the feeling that their naming is just confusing. I still am not sure what exactly is .NET and what's not.

.Net is 14 years old now - if you don't know what it is by now you're probably not ever going to know. It's a cross platform runtime and a group of programming languages that run on it, just like Java.

The general idea of .NET as a platform is easy to understand. The naming of .NET Core, .NET Framework, ASP.NET, etc. and the difference between them is not.

Re: Announcing .NET Core 1.0

#36

A bit unrelated, but I'm hoping to hear something soon about the future licensing model for the upcoming SQL Server on Linux. Do we get a free version without DB size / CPU / RAM limitations (but perhaps with some other restrictions) that smaller companies and startups can use in production? I'm planning to run my future ASP.NET MVC projects on Linux and very much would like to know if a better SQL Server Express / C…

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.

Re: Announcing .NET Core 1.0

#37

A bit unrelated, but I'm hoping to hear something soon about the future licensing model for the upcoming SQL Server on Linux. Do we get a free version without DB size / CPU / RAM limitations (but perhaps with some other restrictions) that smaller companies and startups can use in production? I'm planning to run my future ASP.NET MVC projects on Linux and very much would like to know if a better SQL Server Express / C…

Why limit yourself with Express/ Community if you can get full featured RDBMS with Postgres?

Re: Announcing .NET Core 1.0

#39
post #23

I was expecting they would fix the Uri class on Unix ( https://github.com/dotnet/corefx/issues/1745 ) before releasing 1.0 :( Now I fear their backwards compatibility policies will prevent to fix it later. So much for crossplatformness...

Way too many compatibility issues unaddressed by that PR to have a hope of getting anything changed there. Also it looks like what you (?) are trying to do could easily be solved with the Path.* and Directory.* path manipulation functions. No need to put a million apps at risk when you can wrap your call to Uri() with a three line helper.

Re: Announcing .NET Core 1.0

#40
post #23

I was expecting they would fix the Uri class on Unix ( https://github.com/dotnet/corefx/issues/1745 ) before releasing 1.0 :( Now I fear their backwards compatibility policies will prevent to fix it later. So much for crossplatformness...

They've renamed some packages, so this might possibly be fixed in another one? I found the Ping class didn't work on any non-Windows OS, but it was fixed in a later package with a new name.
Post reply on HN