9 ms·
Microsoft ASP.Net Core 2.0.0 released
- RachelF 9y agoNice, but Microsoft restarting the .NET numbering scheme is going to confuse many, even if they added the word "Core" to it. I guess this is equivalent to ASP.NET 7?
- sundvor 9y agoYou do realise that Core is a complete rewrite of .net, which is platform independent? (Edit: Designed from the ground up to be 100% platform independent) To start Core from 1.0 is (as such) entirely appropriate considering the scope of the project.
- jordanwallwork 9y agoI struggle now knowing what to google when I need to solve a problem! I (stupidly, probably) started the current app I'm working on with the RC and I've gotten totally muddled by the different versions. It doesn't help that things changed so rapidly in those early versions that you had to know exactly which version to search for or the info you found would be totally inapplicable. It's great stuff though, I'm glad I went with it even if it's given me some headaches along the way!
- hudo 9y agoIf its called asp.net 7 people would think its backward compatible. And since almost everything was rebuild from scratch, WebForms doesn't exists, WCF also, most important namespace System.Web is gone, it wouldn't be fair to version it with 7. MVC API looks the same, but that's about it, everything else underneath is new. MS went long way to "emulate" old MVC and WebAPI, for easier porting of old apps.
- NiLSPACE 9y agoI thought major versions aren't usually backwards compatible (.Net 5.0 instead of 4.8)
- benaadams 9y ago.NET runtime breaks with general versioning in that every version is backwards compatible; it follows closer to the Windows versioning where every version of Windows is generally backwards compatible with every prior version.
- dep_b 9y ago> WebForms doesn't exists, WCF also It's not compatible with the stuff that I always found a bit backwards. Good. The amount of time I threw out of the window as a junior developer thinking WebForms was difficult because I didn't really understand it well enough yet is horrible. I hate WebForms.
- vyrotek 9y ago> I hate WebForms Indeed. Things like UpdatePanels were a nightmare to work with sometimes. MVC was a breath of fresh air.
- keithnz 9y agothere's quite a few things they hit the reset on and manage a few things with different version numbers that are all currently on very similar versions. I read a post a while back they know its a problem and plan to improve it. But I don't know.... microsoft seems to have trouble with linear versions!
- dustinmoris 9y agoIn theory it is not ASP.NET 7 because Microsoft refuses to say that ASP.NET Core supersedes ASP.NET, even though in practice this is exactly what they are doing. So in theory there could be an actual ASP.NET 7 in the future which would be different to ASP.NET Core, but my guess is that in practice this will never happen.
- WorldMaker 9y agoASP.NET Core 1.0 was referred to as ASP.NET 5 for months and months before too many complaints about backwards compatibility breaks forced the hand and renamed it.
- Boothroid 9y agoI wish they could come up with some more distinctive naming! Unusual names stick in your head better.
- mariusmg 9y agoI remain unconvinced that .NET Core is not some high ranking Microsoft executive idea of a practical joke.
- bsaul 9y agocare to explain why ? this whole project had me interested again in the .net platform ( although i ended up not jumping ship because i thought the platform wasn't mature enough)
- cheez 9y agoMany developers are excited about .NET core and it being cross-platform. So if it's a joke, everyone is in on it but you.
- sundvor 9y agoYep; couple this with MS publishing how to roll out micro service builds based on Docket, you see Microsoft fully embracing the state of the art of programming. More importantly, they are making these techniques and patterns available and accessible to us developers.
- hudo 9y agoWhy's that? IMHO, its finally some good usable .net. Full fx was ok in 2005, but today Core is the proper framework. Sure, tooling is still half broken (only if you try to do some crazy thing), there's small API surface in Core 1.1, but I have few apps in prod already, and development is good and easy, no major issues or showstoppers.
- camus2 9y agoThe goal is to make a subset of ASP.NET run on third party platforms. It's actually a very good solution for web application development.
- tonyedgecombe 9y agoThe goal is to allow developers to write Azure applications on their Apple computers, anything else is a lucky side effect.
- sundvor 9y agoCongratulations to the team and contributors. My favourite news has to be all the internal perf improvements; can't wait to start using it in my own work, and discover what else is new.
- duncan_bayne 9y agoWhy is this getting down voted?
- caleblloyd 9y agoThis is the ASP.NET Core 2.0 MVC Framework that will run on the .NET Core 2.0 runtime. This is not the .NET Core 2.0 runtime. The .NET Core 2.0 runtime is still in preview for the next month or so. Microsoft released the library specification for .NET Core 2.0, called .NET Standard 2.0 and published all of the GA 2.0 versions of their libraries, such as this one, on Friday August 11. Library maintainers have the next month or so to publish updates to get ready for the .NET Core 2.0 GA release.
- Traubenfuchs 9y agoThe necessity for clarification in this matter is part of the problem.
- UK-AL 9y agoI don't know why it is required. I mean its basically a Django/Python or Rails/Ruby style relationship.
- GordonS 9y agoI guess this was meant to be a gripe about .NET Core vs .NET Standard - but this release isn't about either, it's ASP.NET Core, the web framework. There is no clarification needed in this case.
- 9y ago
- esistgut 9y agoCan anyone compare this to other backend frameworks like Django and Rails? Are non-Windows operating systems well supported as development platforms? I did some quick searches and the standard Visual Studio popped out a lot inside documentation, doesn't seem like a good sign. How would you compare it to Elixir and Phoenix?
- romanovcode 9y agoA lot of documentation is a bad sign to you? Also, non-Windows OS are supported as a first-class citizens.
- cyphar 9y ago> A lot of documentation is a bad sign to you? A lot of documentation that specifically talked about Visual Studio and not any other (more platform agnostic) tooling is probably what made them say it was a bad sign.
- bpicolo 9y agoI've been working with dotnet core the past couple months. It takes a lot of Googling to find useful answers still. The documentation is not particularly comprehensive and it is true that the docs are frequently images of "How to use visual studio to do this" which is never useful for vscode users. I'm actually starting to understand why StackOverflow is such a commonly used resource because of it (in python land I almost never need to defer to stack overflow). That said, still enjoying the ecosystem, but docs-wise it's kind of a mess. I was thinking I'd start compiling a few cheat sheets for things like EF... This page for example is just totally busted: https://code.msdn.microsoft.com/101-LINQ-Samples-3fb9811b https://code.msdn.microsoft.com/101-LINQ-Samples-3fb9811b And that's linked directly from: https://docs.microsoft.com/en-us/ef/core/querying/basic https://docs.microsoft.com/en-us/ef/core/querying/basic
- sitharus 9y agoIt’s been a while since I used Django or rails, but asp.net has the same feature set. Asp.net is more modular than I remember the other frameworks being but that has probably changed in the last few years. With .net core development is supported on macOS and Linux as well as windows with visual studio code. I develop on macOS myself. If you’re not familiar with asp.net it’ll be a bit confusing. There are now two versions - asp.net which is windows only and asp.net core which is cross platform. Also there has been a lot of flux in .net core so older tutorials are often wrong.
- vishbar 9y agoHow is the tooling these days? I played with .NET Core a while ago (before the move away from project.json and just after the move to the dotnet command line tool rather than dnx/dnvm/etc.). I found the documentation for the tooling to be confusing, sparse, and often contradictory. Have things improved? How much manual XML munging is required with the new csproj format, assuming one isn't using Visual Studio and is developing on Mac/Linux?
- romanovcode 9y agoIt's good, the XML is minimal and looks way better then project.json.
- cjsuk 9y agoWell it calls home now unless you argue with it ... https://github.com/dotnet/cli/issues/3093 https://github.com/dotnet/cli/issues/3093
- hitgeek 9y agoit took me a lot of trial and error, but I was able to get a pretty nice asp net core dev env working with the dotnet cli, and vs code. so its possible, but not always easy. documentation is still confusing and contradictory, but a little less sparse. I use the dotnet cli for everything, and rarely need to manually edit the csproj. Even when I do, the csproj is very simple straightforward xml, nothing like the old version. I use node/npm/gulp tool chain for build pipelines. I set up npm wrappers for the dotnet cli, "npm run build", "npm run test", "npm run start", which I like. my favorite thing is that I can reasonably work on c# projects without full Visual Studio and solutions.
- bernadus_edwin 9y agoThis is a good news. But i will not move till ef lazy loading ready
- jrs95 9y agoThat's scheduled for release in 2.1.0
- vyrotek 9y agoIn my experience lazy loading is terrible for application and query performance. The first thing we've done at several companies on many projects is immediately disable lazy loading.
- pjmlp 9y agoI would rather use Dapper, unless one doesn't care about DB performance.
- bernadus_edwin 9y agoThis is a good news. But i will not move until ef lazy loading arrive
- garganzol 9y agoTechnologies related to .NET Core always surrounded by the royal misconception about versioning and communicating those releases to the end customers. 2.0.0? I'm sure a lot of people started to check whether Visual Studio 2017 has a corresponding tooling aka .NET Core 2.0. As always, not yet. Why not just make a cumulative announcement along the lines "Everything-.NET Core-2.0 is out and ready"?
- caleblloyd 9y agoOne benefit is that library maintainers have the next month or so to update their libraries to target .NET Standard 2.0. If the library specification and the runtime were released at the same time, there would be no third party (non-Microsoft) libraries ready for it on day 1.
- caleblloyd 9y agoLooks like .NET Core 2.0 was just released today, so guess it was more like a 3 day difference instead of a month :)
- ChristianGeek 9y agohttps://www.visualstudio.com/en-us/news/releasenotes/vs2017-preview-relnotes https://www.visualstudio.com/en-us/news/releasenotes/vs2017-...
- benaadams 9y agoIts not "officially" released, and has no announcement. This is a link to the version in the package manager so everything can be tested and 3rd party libraries which depend on it can update and be ready for the offical release. Which looks like 18th Sept https://twitter.com/OpenAtMicrosoft/status/894967197176664064 https://twitter.com/OpenAtMicrosoft/status/89496719717666406...
- benaadams 9y agoActually looks like its now: https://blogs.msdn.microsoft.com/webdev/2017/08/14/announcing-asp-net-core-2-0/ https://blogs.msdn.microsoft.com/webdev/2017/08/14/announcin...
- lunchables 9y agoHonest question: why in this day and age would anyone choose to develop web based applications using a microsoft technology? Given their history ("Embrace, Extend, Extinguish") and the additional cost for software licensing, should you want to deploy on a Microsoft platform, what advantage does this have over any other stack?
- wutwutwutwut 9y agoYou already know the answer to this.
- deleted 9y ago[deleted]
- joshuacc 9y agoI develop applications using TypeScript because it is (a) superior to native JavaScript, (b) open source, (c) has a very clear exit strategy in the unlikely event that Microsoft does something stupid with it.
- anoonmoose 9y ago.NET Core is open-source and runs on Linux. C# is a fantastic language, .NET is a great framework. I'd give you a more developed answer but I don't feel like this is a developed question. Everyone has their reasons for using what they use. To act like .NET is instantly useless because of who contributes the most to the product is unreasonable.
- bobjordan 9y agoTBH, I didn't think I'd ever use Microsoft stuff again after moving to a macbook for developing and deploying on Linux. However, the underwhelming macbook hardware of late drove me to purchase a surface book, which I now love. Then, developed a fairly complex python web app that requires anaconda and a GPU based server. One thing led to another, and this week I deployed a python flask/gevent server web app on windows server 2016 using IIS as a reverse proxy. It turns out IIS and windows server is actually great to work with. I'm quite pleased with it all and not a big deal to license a copy of windows server, it is a pleasure to work with. In the future, looking forward to making my next web app with Visual Studio, C# language and .net core framework.
- dblooman 9y agoIs anyone trying any of this on MacOS or Linux? Every time something .Net comes along there only seems to be Windows based examples tied to VS.
- figers 9y agoOur company is running .NET core in production. I code in Ubuntu. Co-worker on windows and another on a mac. All running VS Code. no difference on any of the OS
- jmcqk6 9y agoI'm working on an app where the server side code is all .NET, and has never even been cloned to a windows computer. I'm not sure if it would even run on window,s because that's not been something we've valued while writing it. The code has been written in vim, atom, vs code, and jetbrain rider. You definitely do not have to live in a windows world to work with .NET.
- tboyd47 9y agoCan I use this to make CRUD apps with .NET on a MacBook?
- 0xbear 9y agoStill no Ubuntu PPA or Debian upstream packages. Apparently they don't want people to actually use it.
- b4ux1t3 9y agoUbuntu and Debian are, believe it or not, rather selective. .NET Core isn't "stable" enough for them.
- 0xbear 9y agoPPA is specifically designed for packages that are potentially not stable. And you can find dozens of garbage packages in Debian repo without even trying all that hard.
- Scarbutt 9y agoTo be fair, it has long way to go to reach the tooling, testing and maturity the JVM has in linux.
- b4ux1t3 9y agoThis is kinda what I was alluding to. I don't think it's quite ready for primetime. That said, I wouldn't be against seeing it in, say, Fedora's bleeding edge repos.
- runesoerensen 9y agoBetter link to announcement blog post: https://blogs.msdn.microsoft.com/webdev/2017/08/14/announcing-asp-net-core-2-0/ https://blogs.msdn.microsoft.com/webdev/2017/08/14/announcin... Related .NET Core 2.0 announcement: https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/ https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcin...