Microsoft is on a roll - they've got command line installable packages of the .NET execution environment for all 3 platforms - OSX, Linux and Windows! (<a href="http://get.asp.net/OtherDownloads" rel="nofollow">http://get.asp.net/OtherDownloads</a>)<p>Can't wait to figure out what you can do with this on Linux. Anyone knows? Maybe not desktop apps but Web Apps should be doable at this stage?
While looking around I thought it was cool that Microsoft developers are directly helping popular libraries become compatible with the new .NET Core.<p><a href="https://github.com/castleproject/Core/issues/90" rel="nofollow">https://github.com/castleproject/Core/issues/90</a><p><a href="https://github.com/nunit/nunit/issues/575" rel="nofollow">https://github.com/nunit/nunit/issues/575</a>
This is also a Release Candidate of the ASP.NET web framework.<p><i>edit</i> Actually, the ASP MVC part has also progressed to RC1 as you can see here: <a href="https://github.com/aspnet/Mvc/releases" rel="nofollow">https://github.com/aspnet/Mvc/releases</a><p>Confusingly, the next release is ASP Version 5 and ASP MVC version 6.<p>Also important: "supported on Windows, OS X and Linux"
This would be a lot more exciting if it actually worked with IIS but it looks like they rushed this out, calling it a "release candidate" in order to be able to say it was out in time for the Connect conference without actually hitting the kind of bar one expects from a release candidate.<p>Their github issue pages are full of unresolved issues around problems with ASP.NET 5 and IIS [0][1][2], and the official docs on publishing ASP.NET 5 to IIS have a significant and incomplete list of "common errors" people are encountering [3].<p>Personally, I'm seeing responses from Kestrel when hitting ASP.NET 5 hosted pages under IIS, but they are zero-byte error 404 responses which don't help much. It's all great in Visual Studio but it's a big zero when trying to actually use it for real. This is not a release candidate. At best it's a 9th beta.<p>[0] <a href="https://github.com/aspnet/IISIntegration/issues/14" rel="nofollow">https://github.com/aspnet/IISIntegration/issues/14</a>
[1] <a href="https://github.com/aspnet/Hosting/issues/466" rel="nofollow">https://github.com/aspnet/Hosting/issues/466</a>
[2] <a href="https://github.com/aspnet/Hosting/issues/364" rel="nofollow">https://github.com/aspnet/Hosting/issues/364</a>
[3] <a href="https://docs.asp.net/en/latest/publishing/iis.html" rel="nofollow">https://docs.asp.net/en/latest/publishing/iis.html</a>
> MaxPath<p>Oh, Microsoft finally woke up and supports path longer than 260 chars in dotNetCore. So, the questions when will Microsoft WinAPI & and the Windows Shell/Explorer too? Will we probably have for Windows 11...
Great. I was looking forward to a good alternative with decent syntax to PHP, and now that ASP.NET can run on linux, there's nothing that stops people from using it over PHP.<p>Honestly I wonder what reason would one have to choose PHP over ASP.NET for their apps in a few months / years time.
As someone who has avoided Microsoft in the past, I've found myself in a position to write a few projects lately on the C# .NET platform, and actually find myself eager to have this available on OS X. I actually enjoyed a lot of features of Visual Studio specifically (I realize this isn't coming yet), but the platform itself really just feels pretty nice and natural.
I've been eagerly keeping a close eye on .Net Core. Congratulations to the teams that have been working on this! It's long overdue and I can assure you many others are keenly interested in this.<p>For myself, mainly because as primarily a Python programmer I've been looking for where to move next with the 2/3 split. I've migrated completely to PyPy4 (which is Python2.7) rather than port/test to CPython3 in the last few years. It was worth the migration and testing that was involved.<p>I'm waiting to see if PyPy will announce they are the flag bearers for Python2. If so, I'll most likely continue using it going forward.<p>On the other hand we use .Net and Python at work so while most people would not agree or find .Net Core to be a bit pointless, for me it means I can move my projects and small business to run on my underpowered VPS, utilizing the same well-supported tech stack that many enterprises use.<p>Keeping my head in C# is a good advantage as I'm also interested in Xamarin and Unity (both professionally and personally). Of course, I'm one who does not have any particular grudge against Microsoft. I do prefer POSIX based systems.
For my home business and hobby tech stack I'm currently looking at 1) PyPy4, 2) .NetCore 3) CPython3. While I'm currently running everything on PyPy4, there's a smaller gap between 1 and 2, and a big liklihood of adoption gap between 2 and 3.
Exciting to see the rc released. I've been waiting up until this point to really dive into a project.<p>One of the things that will be a huge barrier for me though is the lack of system.drawing. I've worked in the sign and graphics industry for 8 years and a lot of software I have written relies on system.drawing. The font rendering is crucial. It appears the only feasible option is the mono implementation.(and maybe that is good enough)<p>Looking ahead I'm curious if there will ever be aa coreclr replacement for this? It seems Microsoft closed the open issue regarding this.<p><a href="https://github.com/dotnet/corefx/issues/2020#event-360344181" rel="nofollow">https://github.com/dotnet/corefx/issues/2020#event-360344181</a>