.NET Core 1.0 is now released!
I feel like it's the culmination of all these years of work in .NET and Open Source. This is why I came to work at Microsoft; we wanted to open source as much as we could and build a community around .NET and open source at Microsoft. 15 years and the work of thousands of people later, today we released .NET Core 1.0.
Take a moment and head over to http://dot.net and check out the download page. It's got a really nice place you can try out C# directly in the browser without having to install anything! There's also a great C# Tutorial with interactive browser-based tools as well.
.NET Core 1.0 runs on Windows, Mac, and several flavors of Linux including RedHat Enterprise Linux and Ubuntu. It supports C#, VB (soon), and F# and modern constructs like generics, Language Integrated Query (LINQ), async support and more. The Core Runtime, libraries, compiler, languages and tools are all open source on GitHub where contributions are accepted, tested and fully supported.
Getting started with .NET Core
- If you use Visual Studio 2015 (and remember, Visual Studio Community is free!) you should get VS2015 Update 3 first then install the .NET Core Tools for Visual Studio.
- If you don't want to use VS, consider using Visual Studio Code for free and install the C# extension from the marketplace to get a great code editing experience along with the .NET Core SDK for Windows. Of course, if you're on Mac/Linux/Whatever, go over to http://dot.net and download whatever's right for you!
- If you want all the advanced and specific downloads for .NET or .NET Core, there's a table here.
What is .NET Core? Here's some details from the .NET Blog:
.NET Core is a new cross-platform .NET product. The primary points of .NET Core are:
- Cross-platform: Runs on Windows, macOS and Linux.
- Flexible deployment: Can be included in your app or installed side-by-side user- or machine-wide.
- Command-line tools: All product scenarios can be exercised at the command-line.
- Compatible: .NET Core is compatible with .NET Framework, Xamarin and Mono, via the .NET Standard Library.
- Open source: The .NET Core platform is open source, using MIT and Apache 2 licenses. Documentation is licensed under CC-BY. .NET Core is a .NET Foundation project.
- Supported by Microsoft: .NET Core is supported by Microsoft, per .NET Core Support
.NET Core is composed of the following parts:
- A .NET runtime, which provides a type system, assembly loading, a garbage collector, native interop and other basic services.
- A set of framework libraries, which provide primitive data types, app composition types and fundamental utilities.
- A set of SDK tools and language compilers that enable the base developer experience, available in the .NET Core SDK.
- The ‘dotnet’ app host, which is used to launch .NET Core apps. It selects and hosts the runtime, provides an assembly loading policy and launches the app. The same host is also used to launch SDK tools in the same way.
Here are the major blogs carrying the announcement.
- Announcing .NET Core 1.0
- Announcing ASP.NET Core 1.0
- Visual Studio 2015 Update 3 and .NET Core 1.0 Available Now
We are also releasing .NET documentation today at docs.microsoft.com, the new documentation service for Microsoft. The documentation you see there is just a start. You can follow our progress at core-docs on GitHub. ASP.NET Core documentation is also available and open source.
Sponsor: Build servers are great at compiling code and running tests, but not so great at deployment. When you find yourself knee-deep in custom scripts trying to make your build server do something it wasn't meant to, give Octopus Deploy a try.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Congrats to Scott(s), Damian E, David F and all at Microsoft.
Just one side note: in the screenshot above, from the tutorial, shouldn't it be using the "using" statement like this?
using (HttpClient client ...
Are the languages built-in and just waiting for tooling and templates, or do we have to wait for VB and F# support in an upcoming release?
First, congrats to the whole team on this amazing milestone. Two notes:
1) A note: I was having trouble following along with the debugging step in VS Code, until I tried updating the C# plugin to TODAY's release (6/27/16). You can do this using [Ctrl+P] and then "ext install csharp"
2) A comment: The "File->New..." experience is quite different to .NET 4.X, and a little more guidance around adding .NET library dependencies would be helpful. For example, I was getting compiler errors when I wrote my first line of code in the body of Program.Main, "var dcs = new System.Runtime.Serialization.DataContractSerializer();" until I realized that each of these is now a NuGet package. I remembered reading that it was redesigned as "opt-in" but it still took me some time to figure out what was going on. In my case, it was even more confusing, because I added the NuGet that corresponded to my namespace (System.Runtime.Serialization), and even that wasn't enough, as I needed to bring in System.Runtime.Serialization.Xml. This makes sense from a design perspective - I like it a lot - but it clearly needs more tooling for us dark matter developers, and I'm sure (or at least hope) this is on the roadmap.
One question please: when and how the MCSD Web Developer certificate will be updated to reflect the new technology?
However, this is just the beginning of greater things, here's to everyone involved for making an amazing platform to develop for!
I few month ago i tried to port some db access libraries to vNext.
The biggest problem i found, to my needs, is the lack of support to DataTable and DataRow.
Is there anything, in the new version, which helps to solve the problem?
What can I use instead? (I don't like EF..)
1. sudo apt-get install dotnet-dev-1.0.0-preview2-003121, is the command suggested on the website, but why in the world is it Preview?
2. What's worse is the following error: Unable to locate package dotnet-dev-1.0.0-preview2-003121
Yikes, it doesn't even exist, which is likely a good thing, since it should be out of preview.
I understand there are a LOT of moving parts when shipping for multiple platforms, so any information to get this going, would be helpful.
can you get some news about ssrs reporting in core environment. no clues til the moment.
Thanks you and congrats.
You shouldn't let a lack of DataTable or DataRow be a hindrance. You can and should get by just using a reader and populating some sort of model object, ORM style. That doesn't mean you have to use EF.
re Flexible deployment:
Can I assume core can be installed side-by-side without overwriting anything... if we're still writing... legacy .net work :)
This is a totally new Microsoft we are seeing the last couple of years. It is really nice to see Microsoft embracing and using other systems and services that work, to make their product, .NET in this case, better. Here I'm referring to the use of Github in particular. .NET, Xamarin.Forms etc. are now on Github and I think this will have a major impact on how things are doing in the future.
Another sample is how Microsoft handles documentation. Have you noticed the "Edit on Github" link in top of all Azure documentation pages? Yes, its all on Github, and you have just fix things and submit a Pull Request, if you find a bug or something missing. I see you are doing a similar thing with .NET Core now, and plans are that Xamarin and Unity3d will do the same.
So. Freaking. Awesome!!!
Keep up the good work Scott and Team! Us .NET developers REALLY, REALLY, REALLY appreciate it.
Congrats on the release, Scott!
I follow your work since MVC and was very sceptical, but with hope, and voila !
Congratulations, you rock !
Looking forward to starting to use Asp.Net Core, but unfortunately I still can't.
IIS requires Asp.Net Core Module which, in the downloads we are guided to, is still not released.
When will this IIS module be released?
And a big thank you Scott, for being one of the people that has pushed for this.
Now let's get some understandable docs about run times, platforms, frameworks, libraries and packages, because that's just making my head hurt :(
Additional note from me. After upgrade to VS 2015 update 3, it broke Razor Intellisense. It seems .NET core tools for VS removed MVC from the project template
There is a million users using Cpanel and Plesk in Shared Hosting environment. If ASP.NET become available inside that hosting panels, that will be a big big step for .NET Web Scripting.
Most developers use PHP because it comes with hosting panels.
Any one has ideia if the think will happen?
For this important updates. feeling glad that i am working on.net framework.
So, I think I'll wait a while before before jumping back into this.
I am still pretty confused about DotNetcore 1.0.
I downloaded required things for DotNetCore 1.0.
When a tried to add a new project, i found only 3 project templates :
1) Console Application
2) Class Library
3) Asp.Net core Application.
Well is it so, DotNet core is all about core capabilities of framework.
Like windows services, small executable or so on and henceforth.
And we cannot build applications like we used to in WPF, Winforms or Silverlight may be.
Thanks in Advance.
Comments are closed.