We started to work on project during beta 7 & managed to implement most of functionality in version 1.0.0-rc1-update1. We are mostly using MVC for authenitication and web api to serve data. Most of the functionality is in client-side Angular.
Considering RC2 is now out, we don't have time to upgrade due functional deadline.
So the question is can we go-live with this version or MUST upgrade to RC2?
RC1 had a go-live license however since RC2 has been released RC1 is no longer supported. In other words, if you hit an issue no one will spend time investigating it. Given that the final 1.0 is planned to be shipped in the next few weeks and that changes between RC2 and RTW are minimal moving to RC2 is not a bad idea - it will be quick and easy to move from RC2 to the 1.0.0 final. Here are some resources that will help you migrate your RC1 to RC2:
https://docs.asp.net/en/latest/migration/rc1-to-rc2.html
https://github.com/aspnet/Home/issues/1381
Related
I was looking for some NuGet updates about my project libraries. I see that there are a lot of Microsoft libraries update to v5.0.0.
Based on my knowledge I think these are new dependencies released with .Net 5.0 and I'm not sure that I can update these libraries to latest version using .Net Core 3.1 project.
Can I update to v5.0.0 libraries even if I'm using/building a .Net Core 3.1 project?
Unfortunately, you cannot update many of these newest Nuget packages to 5.0. The reason being is that the newest Nuget package versions are written primarily for .NET 5, and often times Nuget Package Manager will even prevent you from installing them since there are differences in the APIs. With that said, there may be a few spots where it will allow the installation, but I wouldn't recommend it if you plan to keep the application on .NET Core 3.1. Most likely it could cause some inconsistencies that would be hard to debug. Proceed with caution, or upgrade your projects to .NET 5.
I just finished the same. I had 3.1 core application with a lot of 3.1 and NET Standard2.0 libraries projects and just updated all these libraries to the version 5. All libraries were working ok, I could compile them. But I couldn't compile my main Web application. It started to give some strange errors that some staff needs .net5. Maybe it could be fixed but I didn't see much sense to waste my time since in any case I was planning to move to net5 in a couple of days. So I just decided to move to net5 immediately. I had installed net 5.0 SDK and change target framework of my application to net5.0. Now everything is working fine and I am happy with my net5.0 application. I have some Net 4.8 projects that use the same common libraries that I am using for Net Core. So these common libraries are targeted to netstandard2.0. and can't change them to Net5. Now all these Standard2.0 projects still work with my net5.0 web application without any problem. Since I didn't have any problems with my previous version 3.1.9 I DON'T RECOMEND to update libraries to 5.0 if YOU DON'T PLAN to move your application to Net5.0. You can get more problems after this then you can gain from this update.
You should report such (VS for Mac and VS for Windows) as product defects to Microsoft, as many of the new 5.0 packages are targeting net5 solely, and not applicable to netcoreapp3.1.
Try to use outdated tool to check package updates, which is much more reliable,
https://github.com/dotnet-outdated/dotnet-outdated
I have a API that is actively being developed, running on .net core 2.1. Is the idea with .NET Core to constantly be updating my project/code to the latest version of .NET Core?
Now I see that 2.2 is stable. Should I target that, and then when 3.0 is here change to target that?
It's partly a matter of preference and necessity.
If you prefer to stay current and there are no breaking changes, an upgrade is advisable because you have access to new APIs, features, and performance improvements.
If upgrading would break your code due to a breaking change in an API or behavior, or upgrading adds significant maintenance issues to your project, then don't upgrade (at least until you adapt/change your code to deal with the breaking change).
I am new to this ASP.NET versions and I built an app on ASP.NET CORE RC1, MVC6, EF7 & ANGULARJS. I was told that I would need to update the app to use v1 release of .NET Core instead of a release candidate.
I don't know much but that the change was significant with RC1 to RC2, but what do I have to do to update the app for it to work for the .NET Core v1 release?
The changes from RC1 to the recent RTM release are fairly substantial and contain lots of breaking changes (i.e. different API calls, differently named namespaces/packages, etc.) and there isn't really any type of automatic migration process.
Regarding Migrating Your Application
If you want to attempt to migrate your application to the recent release, you should consider checking out Shawn Wildermuth's blog posts on the process :
Migrating from ASP.NET Core RC1 to RC2
Migrating from ASP.NET Core RC2 to RTM
He goes into quite a bit of detail on all of the changes that you need to make that should get your application where it needs to be.
The other option would be to spin up a new ASP.NET Core application and manually migrate some of your existing code into it. This may not necessarily be feasible depending on the size of your project, but for smaller projects it'll likely be an easier and safer route.
Looking at the project.json file in this question and looking at other questions on SO about RC2 makes me think that RC2 has been released. But I cannot find any official announcement that it has been released. Does anyone know if it's been released? If so, can you install it on top of RC1 or are there special installation procedures?
APS.Net Core RC2 will in all likelihood be released on or before 5/17/16 as Damian Edwards mentioned at the ASP.Net Community Stand-up on 5/10/16. As to the link you referenced, they are using nightly builds. You can actually get bits now from the nightly stream that are labeled "Microsoft.AspNetCore.Mvc": "1.0.0-rc3-*" as the team has continued to finish polishing things up for release. These ports will end up being renamed to whatever management decides to call the final build. The Nuget server for Microsoft Nightly builds is https://www.myget.org/F/aspnetcidev/api/v2/ You can add it to Visual Studio by going to Tools=>Options=>NuGet Package Manager=>Package Sources.See NuGet Package Manager Image Here. However, being so close to a supported release version, it seems futile now. I assume Microsoft will support RC2 with a "Go-Live" license.
To be more specific.
ASP.Net Core RC2 will be released ither today (friday), or on tuseday next week.
From what I know, everything is done and set in escrow.
Only the tooling team is tracking a few bugs.
You will find full information here:
https://www.youtube.com/watch?v=P9HqMZviaMg&list=PL0M0zPgJ3HSftTAAHttA3JQU4vOjXFquF&index=0
RC2 will be released in mid-May.
According to ASP.NET Core installation guide:
Before you start
Remove all previous versions of .NET Core from your system.
To do this use Add/Remove programs in Control Panel (Windows).
RC2 you can download from: .NET Core Downloads
Yes, it has been released! You can find the various downloads at: https://www.microsoft.com/net/core
i already built some web applications using asp.net MVC 3 and they work well, and currently i am in the state of starting a new web application for a medical clinic ; but i need to have some advice if i should consider using asp.net MVC 4 beta version instead of asp.net MVC 3?
thanks in advance for any help and suggestions ?
BR
Personally I would start in MVC3 and then upgrade the project to v4 when it's RTMd. Previous versions have had some issues when migrating from Betas (altho see update below).
You can be sure, however, that as with previous version increments, a swift and easy upgrade path will be available (usually there's a project conversion tool released at the same time).
I have a project I'm working on right now, and if I get to the web layer before v4 is finished, I'll be starting in v3 first.
I suppose it does depend, however, on whether any of the new features, such as the adaptive rendering via Mobile views (or indeed the Web API), are intrinsic to your solution. Just don't release on a beta platform :)
Update July 2012
I ended up getting to the web layer of my current project before v4 RTM so decided to go to the RC release first; then the nightly nuget packages for Web API support.
Apart from editor issues (that are documented), I've found no issues, even with integrating a whitelabelling extensibility library I've written, for MVCs 1-3, that operates at a very low level.
Would I have migrated early if I'd not needed the numerous benefits that the Web API provides? Probably not.
But as it is, I'm glad I did :-)
Unless you have a specific reason to use MVC 4 (perhaps a feature that isn't in MVC 3) I would stray away from using beta software for a customer/client. Who knows what bugs/issues you'll have to work around when developing the application or when you upgrade from beta to general release.
There's a reason it's in beta.
As Mackie says.. unless you need a specific feature in MVC4, i'd stay with MVC3. MVC4 is mostly just new features, and has very few changes in the way MVC itself works.
I disagree with Mackie in his comment about "there's a reason it's in beta", in fact MVC4 is very stable and has a go-live license to allow you to use it in production code. It's just that things may still change before final, which is tied more to VS11 than how stable it is.
For my thesis I want to develop an application in ASP.NET MVC, so a few weeks ago I had to make the same decision like you. This is my conclusion:
I should advice to use MVC3 (because it's stable) for your business projects.
There are some known issues ( http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253815 ) in MVC4 beta, so it would be a waste of time to get stuck one day because of beta problems.
When the time is there you'll be able to convert MVC3 with ease to MVC4. So don't hesitate and choose for MVC3 for now. You can decide later on if you want to upgrade or not.
At the link below you'll see how to easily upgrade from MVC3 to MVC4 at this moment: http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253806