Are the latest bits for MVC the Preview 5 release? I've been out of the loop for a while and just wanted to make sure I had the latest and greatest.
Here is the download like: Microsoft ASP.NET MVC Beta
The main site is www.asp.net/mvc
Source code is here: www.codeplex.com/aspnet
You may want to hold off before you do a new install as the Release Candidate is shipping soon (whatever that means). Watch some videos, read some articles ...
Or go get the beta and dive in...
Related
I have recently taken over maintenance of some legacy client projects built with Umbraco 6. I have extensive ASP.NET experience but very little with any version of Umbraco. Unfortunately it seems all relevant documentation has been deleted from our.umbraco.com and any links I've been able to find so far that specifically refer to v6 in the URL, are being silently redirected to v7 docs. This is not at all helpful. An Amazon search only revealed one book published specifically on Umbraco, which dates back to 2011 and doesn't specify which version it covers.
Can anyone tell me if there are any comprehensive API documents or even introductory guides on how to use or develop against this particular version?
Sadly most of the documentation from prior to V7 is either gone or has been redirected to the newer documentation (as you've discovered).
There are probably quite a few older blog posts etc still floating around for the older versions, but I don't know about official content.
The internet archive doesn't appear to have cached any older versions of the documentation sadly. The book that you found will be the one that covers V4, so while it might help a bit, a lot changed in V6 (the introduction of MVC and Razor templates for example).
Some of the V7 docs are still sort of relevant to V6 (specifically the templating stuff and some of the APIs), the main difference is that prior to V7 the back office was entirely web forms, whereas from 7 onwards it was a mix of angular and webforms, before becoming all Angular later on.
There is already 7th beta version of ASP.NET 5, in which they say localization features are done. How can I use localization to write multi-language applications in asp.net 5 mvc 6 with visual studio 2015? Is there any working example project for beta 7 version? I have already searched and found many examples but they no more work because the code has been changed since that. Can I still use .resx files (because visual studio does not auto-generate Designer.cs files any more) or are there any newer or alternative methods they suggest?
Beta 7 introduced the localization, so it's really brand new. I wrote a short write up of everything that is new on my blog. There are a lot of things new, so if you need the features, I recommend reading it.
You can in fact still use Resx, but you have to understand that the resolution by default is, that the engine tries to find the resx file that matches the view.
For example, if you have a HomeController, and an action called Locpage, you need to have Views.Home.Locpage.cshtml.en-GB.resx to Support en-GB locale. The best part, however, is that you don't really need a resx file anymore :-). You can just implement your own implementation of IStringLocalizer and IStringLocalizerFactory, and it'll work. You can see the code for this on my blog, above.
If you want a working sample, the best place right now is their GitHub, so this right here: https://github.com/aspnet/Mvc/tree/dev/samples/LocalizationSample.Web.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Is Asp.net 5 (vnext) ready to use? I just downloaded the VS community version and I am trying to use the asp.net 5 API but it lacks on documentation.
Does anyone know where to find good documentation about creating asp.net 5 web applications?
Latest news
You might have already experienced the pain in migrating from RC1 to RC2 with all its renaming and refactoring.
Even if you started with RC2, you might have already become aware of coming changes that will impact you. For example:
It has now been announced that project.json is gone and we are back to (improved) xml and msbuild as part of the future tooling release. This has lead to discussions on github like this one and posts like this one or this other one.
In short, there are those who think it is still wise to wait even if it is called RC or has a Go Live license. See Hadi Hariri's excellent post for example. Do your research and decide if it is mature enough for your next project!
Release Candidate 2 and RTM
The initial plans were to have RTM 1.0 ready for Q12016 but some fundamental changes are happening between RC1 and RC2, which has had an impact on that initial plan (See for example Scott Hanselman's update on RC2). For up to date info check their roadmap.
As of today (6th May 2016) they have shared an update on the schedule. According to this update, they have decided to split the release of the .Net Core runtime/library from that of the tooling:
.NET Core and ASP.NET Core 1.0 RC2 runtime and libraries will be available in mid-May.
Tooling will be Preview 1 and bundled with this release.
.NET Core and ASP.NET Core 1.0 RTM (release) runtime and libraries will be available by the end of June.
Tooling will be Preview 2 and bundled with this release.
From the same update, we can expect for RC2 .Net Core a Go Live license and official support, but the tooling isn't at the same level:
The .NET Core 1.0 RC2 runtime is a true Release Candidate. It’s solid, stable, and it won’t change for RTM (except if something
critical happens) and we feel good about it. It will have a “go-live”
license, meaning you can get official support from Microsoft.
The tooling that supports .NET Core and ASP.NET Core, including the new command line tools and bits that plug into Visual Studio & Visual
Studio Code, aren’t there yet. It’s going to change before it
stabilizes. We’re going to call this tooling release Preview 1.
Release Candidate 1
Microsoft has recently announced the release of the ASP.Net 5 Release Candidate 1. Details of the announcement here in the official blog.
It now includes a Go Live license:
Starting with the RC1, we are including a “Go Live” license. This
license allows you to deploy an application written with ASP.NET 5 RC1
to a production environment and utilize Microsoft Support. The
duration of this license for the RC1 last until the next release
candidate or the completed release of ASP.NET 5 (called an RTM
release) that is currently scheduled for Q1 2016. This license also
covers running ASP.NET on Windows, Linux, and OSX.
There is also a new site http://get.asp.net/ where you can download the framework. (Which will also be included in VS 2015 Update 1)
Old beta days
ASP .Net 5 is not yet ready for production, is still a beta. From Scott Guthrie's announcement on the latest VS2015 and .Net4.6 release:
The ASP.NET 5 Beta 5 runtime packages are in preview and not
recommended for use in production, so please continue using ASP.NET
4.6 for building production grade apps.
You can check the ASP .Net 5 schedule and roadmap on its github page, where they expect to have the 1.0 version ready in Q1 2016.
Documentation
These are the main places to find more information:
The main documentation site is still under work but growing on docs.asp.net. (And is open sourced!)
You can also check asp.net/vnext for information and tutorials.
Finally, you can check the source code, its tests and tutorial/demo projects in its github repo located in github.com/aspnet.
Should I just be able to install the beta on top of this without problems when it is released ?
Not sure how it is treated within the visual studio environment. I'm thinking with it being a type of project in VS it should be ok.
Can anyone clarify?
MVC 2 is looking to be rather good from what I heard from Scott Gu # the Manchester conference, can't wait for the final release :)
There is always a chance of a breaking change when using preview and beta software. If you want to use MVC 2 Preview, you need to accept the fact that there might be some work in your future to make your project compatable with the Beta, RC, and then Final releases. It won't necessarily break, but the earlier in the release schedule (such as a preview instead of a beta) the greater the chances are you'll have to make changes to your code as they move forward.
When MVC 1.0 previews were released, there were breaking changes between the releases. If you try to keep up with each preview, you should be able to resolve any problems rather quickly - and you could provide great feedback, too!
We have a web app that is using MVC Preview 3. I'm new to the project and relatively new to ASP.NET MVC itself - soon we will be looking to upgrade to either the Beta or RC version.
Are there any major difference between preview 3 and Beta version that would require extensive refactoring?
Any "gotchas"?
From my understanding the RC will be very close to the current Beta... does anyone have a view on this?
Any advice apprecited really.... thanks.
There were quite a few changes between preview 3 to the beta. IIRC the most pain came between preview 3 - preview 4.
One of the biggest gotchas is some of the functionality in the main dlls got placed into a separate dll because they were not going to be fully supported for the first release.
I suggest you brew a large pot of coffee and go and read everything Phil Haack and Scott Gu wrote around that time.
http://haacked.com/archive/2008/07/16/aspnetmvc-codeplex-preview4.aspx
http://weblogs.asp.net/scottgu/archive/2008/07/14/asp-net-mvc-preview-4-release-part-1.aspx
ASP NET MVC - Beta Release Notes has all the details regarding the changes. It is available at the mvc download page.