I was trying to check the latest ASP MVC version, but I got really confused. I was able to understand the problem that happened first when Microsoft declared MVC 5 and then renamed it to MVC Core 1.0.
Still I see now in Microsoft documentation for the regular .NET framework they only mention MVC version 5 as the latest version, while on the web everywhere I would find topics about what is new in MVC 6.0, which has the famous feature of removing dependency over System.Web. Also 6.0 is mentioned on Wikipedia with release date for rc1 as 18 Nov 2015
So is it called MVC 6 by Microsoft or still they call it 5? what is the latest dlls versions for MVC?
There is asp.net-mvc-5.2.3 which is last version before they went to asp.net-core-mvc. Web API 2.2 also shares the 5.2.3 version number. Check Nuget
MVC 6 was originally part of ASP.NET 5 and suppose to be the next version, but due to major changes in the code base, it was decided that it needed to become its own new framework, they decided to change its name from ASP.NET 5 to ASP.NET Core. which is the suggested latest version to use going forward for new projects.
ASP.NET Core MVC 3.1.1 released on 14 January 2020 is the latest ASP.NET MVC version. Post-release of ASP.NET MVC 5.2.7 on 29 November 2018, Microsoft decided to release the next version (with major changes) under the ASP.NET Core MVC category.
Related
Now that .Net Core 3.0 has released what's the story for Azure Functions on core3?
When I try to flip a project to
<TargetFramework>netcoreapp3.0</TargetFramework> it still reports as running on 2.2.
If I try to access an api that's 3.0 only it explodes, which makes sense since it seems to be forcing it's runtime despite the project settings.
Azure Functions is not available for .NET CORE 3 yet. For more information check here
Update
The Azure Functions 3.0 preview is now available!
Please see this post for instructions on how to use the preview on Azure and how to use the 3.0 tools locally:
https://dev.to/azure/develop-azure-functions-using-net-core-3-0-gcm
Update 2
The Azure Functions 3.0 are generally available since December 9, 2019.
For migration instructions refer to docs: https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions
Yesterday (09.12.2019), Microsoft announced the Azure Functions 3.0 go-live release which supports .NET Core 3.1 which has a Long Term Support (LTS).
On March 3, 2020, the Support for .NET Core 3.0 ends - so for anyone reading this, you should use .NET Core 3.1 and Azure Functions 3.0
Further reading: How and why you should upgrade your .NET Azure Functions to 3.0
I need to integrate Angular 6 or 7 (latest version at the time of this writing is 7.0.3) with an ASP.NET MVC 5 application (.NET Framework 4.5+, no .NET Core).
Is Node.js a "must have" in order to run Angular? I need to install the "smallest possible environment" to achieve my goal.
I must also use TypeScript (v3) but not Javascript. Is that possible? Any suggestions?
Many thanks in advance.
EDIT: I looked for a VS 2017 Community Edition project template but most of them are for .NET Core. It would be great if you point to a download location of such a template (ASP.NET MVC 5, TypeScript, Angular 5-7, no Node.js).
I have this issue in which I'm currently targeting .NET Framework 4.7.2 in my solution but the Azure Web App Service only supports up to .NET Framework 4.7.1. So, my question is this: As long as I only use 4.7.1 features, should it work without issue on the Azure Web App Service (which only supports up to 4.7.1) even though I'm targeting 4.7.2? Are the .NET Frameworks backwards compatible? So far, I haven't seen any issues. I just want to make sure there will be no future complications. Ideally, I would like to keep targeting 4.7.2 so that I can start using the 4.7.2 features once it becomes available on Azure Web App Service.
The .NET Framework 4.7.2 builds on previous versions of the .NET Framework 4.x by adding many new fixes and several new features while remaining a very stable product.
The .NET Framework 4.7.2 is included with the Windows 10 April 2018 Update
The .NET Framework 4.7.2 can be used to run applications built for the .NET Framework 4.0 through 4.7.1.
Azure App Service now supports 4.7.2
I think that you did a good thing in upgrading and targeting .NET Framework 4.7.2 ; I also have an Azure App Service and upgraded it to 4.7.2 and it is running very well. As said before, it brings updates and fixes, and it is backward compatible on almost all cases.
Note that the recommended is that the target machine have a .Net version Equal or Greater of the of the .NET Framework 4.x than your compiled version.
See:
https://learn.microsoft.com/en-us/dotnet/framework/whats-new/index#v472
https://learn.microsoft.com/en-us/dotnet/framework/install/on-windows-10
#TheDude, you cannot build an app on 4.7.2 and hope to run it on lower version like 4.7.1. At runtime the target framework version check will fail as it will find the Framework version (4.7.2) as missing.
The other way round (i.e. target 4.7.1 and run on 4.7.2) is fine as the higher versions are backwards compatible.
I have a C# Windows Forms application that makes use of SQL Server 2008 R2, .NET Framework 4, .NET Framework 4 Client, and Entity Framework Code First.
SQL Server 2008 R2 Express exists on the machine, and the program does create the database and tables.
[Update]
I tried installing .NET framework 4.5, but I got this message:
Blocking Issues:
The .NET Framework 4.5 is not supported on this operating system.
Warnings:
Setup may not run properly, because the Windows Modules Installer
Service is not available on this computer.
with this link
The operating system is Windows XP 2002 SP3 running inside VMware Player.
[Update 25th May 20xx]: I found a link here that caused me to think the problem is just that ClickOnce won't install on Windows XP. However I recreated the set up in Visual Studio 2010 and have the same error.
[update 26 May 20xx]: I created a test project with Visual Studio 2012 and Entity Framework 5 and was able to successfully install on Windows XP using ClickOnce. Strangely I was then able to publish a version of my big application that worked.
I am not sure what is going on. I also did install a program containing Entity Framework 6 on my test computer - but this would not have been referenced by my big application.
Have you tried installing .NET 4.5?
I know it sounds absurd, but we're seeing the same issue: Entity Framework 5.0 (4.4) targetting .NET 4.0, Code First on SQL Server CE.
Installing .NET 4.5 made the issue go away. We're still investigating, because we also have a couple of Windows XP clients.
Update:
Portions of the Entity Framework 5 code are part of the .NET framework itself (that's why there's a 4.4 version for .NET 4.0 that e.g. doesn't support enums, while the 5.0 for 4.5 does).
It seems this issue is related to that since installing .NET 4.5 inexpliccably solves this.
For Entity Framework 6 those portions were moved to Entity Framework, so Entity Framework 6 doesn't depend on framework specifics anymore. We've updated to Entity Framework 6.0 alpha 3 and everything seems fine.
Now, I don't like running alpha code, but this is the only solution we could find.
Is there any IIS version release after IIS 7.5?
And is there any update for .NetFramework released after .NetFramework 4?
IIS is considered part of the operating system, so probably IIS vNext will only come when Microsoft releases its next version of Windows, which may not happen in the coming months. But once Microsoft provides public betas of it, you can test it out.
.NET 4 is still the latest, and like #Pawan pointed out, there are updates for .NET already, but SP1 is not yet announced.