News for hackers. Stuff that matters.
Re:Announcing .NET Core 1.0 by jderick on Monday June 27, 2016 @11:48AM (#11986953)
Does this represent some kind of change for .NET? Why is it called 1.0?
Re:Announcing .NET Core 1.0 by judah on Monday June 27, 2016 @11:54AM (#11986994)
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 Foundation (WPF), and excludes some other Windows-specific functionality.

Additionally, this is the first version of .NET in which apps can be totally self-contained. Previously, you'd need to install the .NET Framework on your machine to run .NET apps. That is no longer a requirement in .NET Core 1.0.

So, it's a pretty huge release. And really the first time in decades that MS has built it's premier dev stack with multiple OS support.

[0]: https://github.com/dotnet/core/blob/master/release-notes/1.0...

Re:Announcing .NET Core 1.0 by lotsoflumens on Monday June 27, 2016 @01:44PM (#11987887)
>>> it's the first version of .NET that can build self-contained apps

I tried it - it puts 50MB of DLLs beside the "HelloWorld" executable in a subdirectory (on Ubuntu 16.04).

It's like shipping the entire Java runtime with every app.

Re:Announcing .NET Core 1.0 by judah on Monday June 27, 2016 @02:46PM (#11988443)
>> "I tried it - it puts 50MB of DLLs beside HelloWorld"

That's a bad test for a framework. It's like saying, "I bought an $80,000 car to drive to my neighbor's house across the street - I could have just walked!"

A good test is, "What is the full install size of a real app built on .NET Core?"

And the answer is, not much larger than any other app. All that code has to live somewhere, either in your app or in your libraries.

Re:Announcing .NET Core 1.0 by jimjimjim on Monday June 27, 2016 @04:34PM (#11989254)
well, people complained when Go produced 2mb hello worlds.
Re:Announcing .NET Core 1.0 by osullivj on Monday June 27, 2016 @12:04PM (#11987064)
Interesting. I'm guessing it doesn't support COM interop?
Re:Announcing .NET Core 1.0 by ramenmeal on Monday June 27, 2016 @12:44PM (#11987410)
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 by int_19h on Monday June 27, 2016 @05:14PM (#11989553)
Mono supports COM interop on Linux, too. At its most basic level, COM is really just an ABI, and there's nothing Windows-specific about it (see also: XPCOM).
Re:Announcing .NET Core 1.0 by rbanffy on Monday June 27, 2016 @02:00PM (#11988030)
I remember working with COM on MacOS 8... And it supported remote objects, so, it'd be, in theory, possible to self inflict that pain.
Re:Announcing .NET Core 1.0 by lotsoflumens on Monday June 27, 2016 @02:08PM (#11988081)
I experience a physical revulsion just thinking about all the wasted years I spent with COM and DCOM.
Re:Announcing .NET Core 1.0 by dreamsofdragons on Monday June 27, 2016 @12:42PM (#11987395)
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 by rbanffy on Monday June 27, 2016 @01:59PM (#11988013)
Probably, and it should be considered a feature.
Re:Announcing .NET Core 1.0 by WorldMaker on Monday June 27, 2016 @11:55AM (#11986999)
.NET Core is the new modular, open source rebuild of the .NET Framework. It's a lot of big changes, enough so that they decided to call it a 1.0 to acknowledge that A) it's a big new effort, but also B) it's not entirely equivalent to the full, previous .NET Framework it is intended to eventually replace.
Re:Announcing .NET Core 1.0 by dragonwriter on Monday June 27, 2016 @12:29PM (#11987262)
Its the first non-preview release of the product called ".NET Core"; it is, therefore, versioned as ".NET Core 1.0".

This is a different (but related) product to the .NET Framework (current version, 4.6) -- future versions of the .NET Framework will be built on top of .NET Core, which will be updated more frequently than the larger Framework. So, maybe .NET Framework 5.0 will be built on something like .NET Core 1.3 -- or 2.0, whatever.

Re:Announcing .NET Core 1.0 by malekpour on Monday June 27, 2016 @11:53AM (#11986984)
They reset versioning to 1.0 by renaming .NET to .NET Core
Re:Announcing .NET Core 1.0 by FLGMwt on Monday June 27, 2016 @12:01PM (#11987039)
The full .NET framework (Windows only) will live on, currently at 4.6.2, I believe. ".NET Core" is the new open source, cross-platform subset of the full .NET framework.
Re:Announcing .NET Core 1.0 by insulanian on Monday June 27, 2016 @12:19PM (#11987170)
IMHO the full .NET is from today considered a legacy platform. I would compare the situation to WebForms / MVC - who does new projects with WebForms now?
Re:Announcing .NET Core 1.0 by oblio on Monday June 27, 2016 @12:36PM (#11987331)
As far as I remember the long term plan is to stack the remaining APIs from the full .NET on top of .NET Core.

So Microsoft would have: .NET Core - base for everything. .NET - Windows specific bits, Xamarin - mobile specific bits.

Re:Announcing .NET Core 1.0 by enricosada on Monday June 27, 2016 @11:53AM (#11986982)
Because it's the first version of the xplat .NET (the .NET Core) supported by Microsoft (mono already does an amazing works as xplat, and have done that for years). It's not confusing if you work in .NET, the .NET Framework 1.0 was released in 2000..
Re:Announcing .NET Core 1.0 by jsingleton on Monday June 27, 2016 @11:53AM (#11986988)
It's v1.0 of the "Core" open-source rewrite.