Mvc

[Archived] ASP.NET Core MVC is a model view controller framework for building dynamic web sites with clean separation of concerns, including the merged MVC, Web API, and Web Pages w/ Razor. Project moved to https://github.com/aspnet/AspNetCore

Web Development

Explore on GitHub Read Hacker News discussions

4Distinct people

4Mentions

0Explicit recommenders

5.6KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

dotnet/coreclr · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2015-11-18 16:11:50 UTC to 2016-09-06 06:06:46 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Nov 2015	2015-11-01 00:00:00 UTC	2015-12-01 00:00:00 UTC	1	1
Dec 2015	2015-12-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	0	0
Jan 2016	2016-01-01 00:00:00 UTC	2016-02-01 00:00:00 UTC	0	0
Feb 2016	2016-02-01 00:00:00 UTC	2016-03-01 00:00:00 UTC	0	0
Mar 2016	2016-03-01 00:00:00 UTC	2016-04-01 00:00:00 UTC	1	1
Apr 2016	2016-04-01 00:00:00 UTC	2016-05-01 00:00:00 UTC	0	0
May 2016	2016-05-01 00:00:00 UTC	2016-06-01 00:00:00 UTC	0	0
Jun 2016	2016-06-01 00:00:00 UTC	2016-07-01 00:00:00 UTC	1	1
Jul 2016	2016-07-01 00:00:00 UTC	2016-08-01 00:00:00 UTC	0	0
Aug 2016	2016-08-01 00:00:00 UTC	2016-09-01 00:00:00 UTC	0	0
Sep 2016	2016-09-01 00:00:00 UTC	2016-10-01 00:00:00 UTC	1	1

What Hacker News says

4 sources

colemickens·Sep 6, 2016

>We ended up using the JsonProperty attribute on some things to force their casing how we needed them. That's a weird choice. It's a one-line modification to change back to the legacy naming scheme [1]. (Which is completely non-standard and doesn't follow what basically the entire rest of the web accepts as the standard method of naming js object keys. But hey, .NET people are really beholden to some strange things.) [1]: https://github.com/aspnet/Mvc/issues/4842

In Lessons Learned while Converting from ASP.NET to .NET Core

jongalloway2·Jun 28, 2016

Yeah, please try again. The problem with a lot of Connect programs is that they were tied to a specific release (MonkeyManager Pro 2008) so bugs that didn't make the cut for the product release just got lost in space (not picked up for MonkeyManager Pro 2010). Part of the reason was that there were always internal bug tracking systems, which was what the dev team was really working from day to day, and these other systems were just inputs to that. If you look at any of the projects that are on GitHub now, the public issues list is the issues list. You can see all the dev comments, scheduling via labels, pull requests, code reviews, etc. https://github.com/aspnet/mvc/issues?q=is%3Aissue+is%3Aclose... https://github.com/dotnet/coreclr/issues?q=is%3Aissue+is%3Ac... For products that aren't on GitHub, public issue lists like UserVoice have st

Read the rest

ill been a big improvement (in my opinion) because they usually keep the bugs / issues / feedback around until it's fixed, and the votes accumulate so the important issues keep bubbling up.

In Announcing .NET Core 1.0

rubber_duck·Mar 21, 2016

See this is exactly what I'm talking about ! I can't blame you for not being up to date with developments on .NET platform or in the Microsoft world - but please o please refrain from making comments about the issue you are not informed about and obviously haven't looked in to for the last couple of years. Microsoft has their own cross platform open source .NET implementation under MIT license supported officially on Linux and OSX. https://github.com/dotnet/coreclr Not only that but they are opensourcing and porting huge parts of their stack like build system, web framework, etc. and are supporting it officially on Azure cloud. https://github.com/aspnet/Mvc They are doing pure OSS from scratch projects such as LLILC - a static compiler for CoreCLR based on LLVM : https://github.com/dotnet/llilc Further more even before that Microsoft has

Read the rest

started opensourcing large parts of their implementation at the request from Mono team and Mono has taken those + CoreCLR and made their implementation better - showing that they actually wanted to help Mono team implement feature parity. And finally Microsoft recently acquired the Mono team (Xamarin) and will probably fold that in to their OSS offerings. So please stop the FUD - it's not helping anything - I realize you have an opinion but before voicing it please check if it matches the facts - otherwise you're just creating noise in the discussion.

In The Deep History of Your Apps: Steve Jobs, NeXTSTEP, and Early OO Programming

SideburnsOfDoom·Nov 18, 2015

This is also a Release Candidate of the ASP.NET web framework. edit Actually, the ASP MVC part has also progressed to RC1 as you can see here: https://github.com/aspnet/Mvc/releases Confusingly, the next release is ASP Version 5 and ASP MVC version 6. Also important: "supported on Windows, OS X and Linux"

In Announcing .NET Core and ASP.NET 5 RC