Why is there not a Microsoft.AspNetCore.Mvc.ViewFeatures, Version 6.0.0.0 in NuGet?

Question

Unable to use assembly Microsoft.AspNetCore.Mvc.ViewFeatures, Version 6.0.0.0 in Azure Functions project. I need the ViewResult to support the view model in a Blazor client application. The latest Microsoft.AspNetCore.Mvc.ViewFeatures I can add via NuGet is Microsoft.AspNetCore.Mvc.ViewFeatures, Version 2.2.0. With this I get a Compiler Error CS1705.

Error CS1705 Assembly 'Csla.AspNetCore' with identity 'Csla.AspNetCore, Version=6.0.0.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30' uses 'Microsoft.AspNetCore.Mvc.ViewFeatures, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' which has a higher version than referenced assembly 'Microsoft.AspNetCore.Mvc.ViewFeatures' with identity 'Microsoft.AspNetCore.Mvc.ViewFeatures, Version=2.2.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' Arms.AzureFunctions D:\dev\Pawportunities\Arms.AzureFunctions\CSC 1 Active

Why is there not a Microsoft.AspNetCore.Mvc.ViewFeatures, Version 6.0.0.0 in NuGet?

Answer 1

the nuget package was moved to asp.net core 6 framework, so it is no longer required. many of the asp.net core nuget packages were moved and are now more interdependent.

just remove the package from the project

Answer 2

the Microsoft.AspNetCore.Mvc.ViewFeatures.dll is in the Microsoft.AspNetCore.App runtime folder. Not sure if you can get aspnetcore library to work with the azure functions. one of the features of the aspnetcore runtime, is it can update core features.

you may need to deploy as web app rather than a azure function. you certainly can call it from an azure function.

Answer 3

My Azure Functions project was based on <Project Sdk="Microsoft.NET.Sdk"> . I updated the Sdk reference to be <Project Sdk="Microsoft.NET.Sdk.Web">. This added Microsoft.AspNetCore.App.Ref under the dependencies frameworks. Now I can reference the Controller that is part of Microsoft.AspNetCore.Mvc.ViewFeatures.