4 ms·

Does this represent some kind of change for .NET? Why is it called 1.0?

by jderick 10y ago

enricosada 10y ago
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..
malekpour 10y ago
They reset versioning to 1.0 by renaming .NET to .NET Core
- FLGMwt 10y ago
  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.
  - insulanian 10y ago
    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?
    - oblio 10y ago
      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.
jsingleton 10y ago
It's v1.0 of the "Core" open-source rewrite.
judah 10y ago
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/1.0.0.md https://github.com/dotnet/core/blob/master/release-notes/1.0...
- osullivj 10y ago
  Interesting. I'm guessing it doesn't support COM interop?
  - dreamsofdragons 10y ago
    https://docs.microsoft.com/en-us/dotnet/core/api/system.runtime.interopservices https://docs.microsoft.com/en-us/dotnet/core/api/system.runt... Though I'm not sure it's of any value outside of Windows.
  - ramenmeal 10y ago
    If you need COM interop, you don't need cross platform compatibility. You can just use the full .Net framework.
    - rbanffy 10y ago
      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.
      - 10y ago
WorldMaker 10y ago
.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.
dragonwriter 10y ago
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.

Does this represent some kind of change for .NET? Why is it called 1.0?

by jderick 10y ago

Does this represent some kind of change for .NET? Why is it called 1.0?

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..

malekpour 10y ago

They reset versioning to 1.0 by renaming .NET to .NET Core

FLGMwt 10y ago
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.
- insulanian 10y ago
  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?
  - oblio 10y ago
    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.

jsingleton 10y ago

It's v1.0 of the "Core" open-source rewrite.

judah 10y ago

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/1.0.0.md https://github.com/dotnet/core/blob/master/release-notes/1.0...

osullivj 10y ago
Interesting. I'm guessing it doesn't support COM interop?
- dreamsofdragons 10y ago
  https://docs.microsoft.com/en-us/dotnet/core/api/system.runtime.interopservices https://docs.microsoft.com/en-us/dotnet/core/api/system.runt... Though I'm not sure it's of any value outside of Windows.
- ramenmeal 10y ago
  If you need COM interop, you don't need cross platform compatibility. You can just use the full .Net framework.
  - rbanffy 10y ago
    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.
    - 10y ago

WorldMaker 10y ago

.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.

dragonwriter 10y ago

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.