Announcing .NET Core 1.0

Post by knocte » Mon, Jun 27, 2016, 4:55 PM UTC

tacos wrote: post #39

knocte wrote: 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.

Post by jsingleton » Mon, Jun 27, 2016, 5:10 PM UTC

daveguy wrote: post #67

FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…

Post by [deleted] » Mon, Jun 27, 2016, 5:16 PM UTC

RomanPushkin wrote: post #52

AndreyErmakov wrote: post #19

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…

You can go ahead with PostreSQL if you use Entity Framework and Code First approach. I used it many times and I was able to quickly jump from PostreSQL to MS SQL and back. It just works. With EF I don't see any reason why I should tie to any particular SQL database

Post by akavel » Mon, Jun 27, 2016, 5:17 PM UTC

pjmlp wrote: post #81

gldev wrote: post #4

After so many years microsoft finally presenting their tools in a more moden way. Never been a huge fan of .NET but i can't deny is a great tool hopefully people try it out on more platforms.

I went full circle, from a critic how they cloned Java back when my employer had the privilege to beta test .NET as a Microsoft partner, to someone that enjoys delivering solutions on the .NET stack. For me the sweet spot will be when .NET Native becomes more mature and I can get Delphi/Modula-3 back.

Post by brudgers » Mon, Jun 27, 2016, 5:23 PM UTC

wvenable wrote: post #85

daveguy wrote: post #67

FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…

Microsoft is looking to do more data-driven design; this is the reason for all the telemetry in Windows as well. Raymond Chen pointed out an example where a button was removed File Explorer (prime real-estate) because the telemetry showed that hardly anyone ever pressed it. It's unfortunate they are so tone-deaf about the PR implications in Windows.