Live data from Hacker News

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

71–80 of 327 posts

Re: Announcing .NET Core 1.0

#71

Earlier quoted context omitted.

First line of the blog post: We are excited to announce the release of .NET Core 1.0, ASP.NET Core 1.0 and Entity Framework 1.0, available on Windows, OS X and Linux!

Interesting, I could swear that the first time I clicked the link it went to a product page. I never saw the blog post.

You're right, the link was updated after the announcement post was made public (was https://www.microsoft.com/net/) :)

Re: Announcing .NET Core 1.0

#73

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.

Sure it's obvious. Like I said I "get it" it's just core has always been a part of .Net just less directly referred to so my first thought was this was .Net 1.0's core until I started reading through the link.

Overall I think it's a good move just a little confusing (unless I'm the only one) for those who have done .Net work before.

Re: Announcing .NET Core 1.0

#74
post #18

Earlier quoted context omitted.

It's the first version of .NET that's cross-platform, it's the first version of .NET that's totally open source, and it's the first version of .NET that can build self-contained apps (no need to have .NET Framework installed to run .NET Core 1.0 apps). See the release notes[0] for more info. It's called "core", because it doesn't contain the Windows desktop UI toolkits, like Windows Forms and Windows Presentation Fou…

Interesting. I'm guessing it doesn't support COM interop?

https://docs.microsoft.com/en-us/dotnet/core/api/system.runt...

Though I'm not sure it's of any value outside of Windows.

Re: Announcing .NET Core 1.0

#75

Good news! Now time for all the library and framework authors to add support for .NET Core. I know a lot of people were waiting for RTM before starting this, considering the massive changes between RC1 and RC2. I've started a support matrix project at https://anclafs.com . Feel free to file an issue or send a PR on GitHub.

the asp.net core changed a lot between rc1 and rc2 (because moved to .net sdk instead of dnx). The normal libraries or console app not too much

Re: Announcing .NET Core 1.0

#76
post #18

Earlier quoted context omitted.

It's the first version of .NET that's cross-platform, it's the first version of .NET that's totally open source, and it's the first version of .NET that can build self-contained apps (no need to have .NET Framework installed to run .NET Core 1.0 apps). See the release notes[0] for more info. It's called "core", because it doesn't contain the Windows desktop UI toolkits, like Windows Forms and Windows Presentation Fou…

Interesting. I'm guessing it doesn't support COM interop?

If you need COM interop, you don't need cross platform compatibility. You can just use the full .Net framework.

Re: Announcing .NET Core 1.0

#78

I was really hoping for ARM support at least as far as RasPi goes for 1.0. But still very good news I personally love .Net it's nice to be able to use it cross platform without having to work specifically around mono.

From what I see Samsung has been contributing on that front. They said in the announcement that Samsung has joined the Dotnet Foundation.

Re: Announcing .NET Core 1.0

#79

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.

Good point, I meant MVC6. I confused the versions of ASP.NET 5 (which is now known as ASP.NET Core) and MVC6.
Post reply on HN