Autofac MultiTenant with ASP.NET MVC3 - asp.net-mvc-3

Which version of Autofac supports MultiTenant for ASP.NET MVC 3? I could find this for ASP.NET MVC 4

The last version of Autofac released that supported MVC3 was 2.6.3. Not all packages were released on NuGet at that time; that happened starting with 3.0. The last time the Contrib packages (which contain the multitenant library) were released on the 2.6 line was 2.6.1.
If you need an MVC3 stack, you'll need to go to the Autofac download list, switch the search filter to "Deprecated Downloads" and search for "contrib" - pick the latest version you can find of the contrib packages. It looks like 2.6.1 is it. Then search for "2.6.1" to find the corresponding core assemblies.
Autofac has a general policy of staying current, so as new MVC releases are put out, older releases stop getting direct support. There is no version of Autofac 3.0 that has MVC3 support and there is no plan to back-port functionality.
Note that the multitenant support isn't specific to a project type. It is a single library that supports any application type. What you really want is a version of Autofac that supports MVC3 and has a corresponding build of the multitenant plugin library. Hopefully the instructions above provide that.

Related

What Non-4.* .NET App Versions play well with Standard?

I am building an MVC Web API (Service) with Views returned in specific cases. As an architectural decision, I've been directed to NOT build the service project in .NET Framework 4.*. Rather, I am to attempt .NET 5.0 first, and then Core 3.1 if 5.0 doesn't work.
This service project in my solution will depend on a few class library projects, call them DataLibrary, ComplexLibrary, and DocLibrary. DataLibrary will depend on a Nuget package of Oracle, be it ODP or Oracle Managed Data, in order to query an Oracle database via an Oracle Package on that database. DocLibrary will depend on a Nuget package of Aspose Word & Aspose PDF. ComplexLibrary will depend on Oracle AND Aspose.
Here's my dilemma:
Aspose Word's latest stable release (21.6) will report that it is compatible with 5.0 and Standard 2.0, but not .NET Core.
Oracle Managed Data reports that it is compatible with Standard 2.1 or Standard 2.0, but not 5.0 or .NET Core.
My own libraries have reported that they are not compatible with my API .csproj if...
3a. The API is 5.0 and the libraries are .NET Core or .NET Standard
3b. The API is Core 3.1 and the libraries are .NET Standard.
Since my compile script naturally requires a run of Nuget to retrieve all the necessary dependencies, I cannot get a clean compile because I seemingly have no combination of versions for my WebAPI and libraries that satisfy each others' compatibility needs. Since Standard libraries are the only common .NET version that satisfy the needs of both Aspose & Oracle, What available version for my WebAPI (i.e. I don't believe that Standard is an option for anything other than a class library) is compatible with .NET Standard libraries?
Thanks.
Please see the following article https://learn.microsoft.com/en-us/dotnet/standard/net-standard.
.NET Standard is not a framework it is kind f specification and .NET Core, .NET 5, Mono framework etc are .NET Standard implementations.
So for library projects I would select .NET Standard and for the service .NET Core or .NET 5 (which is actually the next version of .NET Core)
Well, don't I feel silly.
Turns out, the issue wasn't incompatibilities within Aspose, Office, .NET Core, 5.0, and Standard, but a failure of a prior version of NuGet to handle the different versions.
While my VS 2019 install was able to compile the whole solution effectively, my local install of NuGet was not. This was due to VS2019 likely using the most up-to-date version as of this post (5.9.#), while my locally installed version was 4.9.#. Thus, VS was able to sail through while my compile script kept failing at the NuGet stage (which I have included prior to the actual compile.) Once I ran a NuGet update, everything was good to go.
Long story short: KEEP YOUR NUGET VERSION UP-TO-DATE!!!

Kendo for .net Core 3.1

I try to use Kendo in my Razor Pages app, I followed this doc https://docs.telerik.com/aspnet-core/getting-started/first-steps, but I have error:
System.AggregateException: 'Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Kendo.Mvc.Rendering.IKendoHtmlGenerator Lifetime: Transient ImplementationType: Kendo.Mvc.Rendering.KendoHtmlGenerator': Could not load type 'Microsoft.AspNetCore.Mvc.Internal.ClientValidatorCache' from assembly 'Microsoft.AspNetCore.Mvc.Core, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.)'
I'm using Telerik.UI.for.AspNet.Core, version 2019.1.220.
I'm going to add my comment as an answer, because this Telerik thread confirms (and references the same error you are encountering) that you'll need a later version of Kendo to have support for .NET Core 3.1.
This quote here from the thread linked above - about .NET Core 3.0 requiring a later version than you are using:
Artem, that is correct. Only the latest version of the UI for ASP.NET
Core suite (2019.3.1023) offers official support for .Net Core 3.0.
Jerry, feel free to contact us if you have any further questions on
the .Net Core 3.0 integration.
Regards, Veselin Tsvetanov
R3 2019 is the first release that mentions full support for .NET Core 3.1.

How to convert NetFramwork 4 code to NetCore 2?

I have a C# project which was created using NetFramework 4.6. I want to convert it to using the NetCore 2.1.
I checked the network, and people say I can just change the Target Framework value in the project's properties page. But on my computer, I cannot see options for NetCore.
I already have the NetCore 2.1 SDK installed.
Is there another way to convert the project? Is there something wrong with my project that prevents it getting converted?
People are wrong, there is no such "one step" approach.
Remember that .NET Core is not a higher version of .NET Framework, it is rather a rewrite from scratch. So it does not work like retargeting .NET Framework version form 4.0 to 4.5.
Porting to .NET Core from .NET Framework is a good place to get started.
Edit: This page lists some differences between .NET Core and .NET Framework.
You can't do this simply like this; because of their totally different frameworks, not different versions of same framework. You have to port your project to .net core; there is one of the nice extension for visual studio that generate a report for you about how portable your code is between .NET Framework and .NET Core.
This is also one of the article about the issue that may be useful for you.

Changelog difference between version 2.3 and 3.0

I tried the application framework for a while using version 2.3
Now I'm planning the development of 2 web applications (MPA with ASP.NET MVC 5.x
)
What's the differences between version 2.3 and 3.0 version?
I didn't found any changelog files
Changelog
The release notes for the framework (ABP) can be found here: https://github.com/aspnetboilerplate/aspnetboilerplate/releases
The release notes for the template (MPA with ASP.NET MVC 5.x) can be found here: https://github.com/aspnetboilerplate/module-zero-template/releases
Notable differences
Most importantly, ABP v3.0.0 is based on .NET Standard 2.0.
This concerns you regardless if you are on MVC 5.x, .NET Framework 4.x or .NET Core 2.x.
You should use VS2017 15.3.3+.
For VS2015, you may try installing NuGet client 3.6 or higher but that may no longer work.

reference is not added in ASP.Net MVC 6 for "Microsoft.BingAds.SDK”

I am doing this project in mvc6 using asp.net framework 6.how I can add this reference in my project please help me.
You have to talk to BingAds and ask them for a compatible version. This is the same with every library provider, they all must support the new platform. You cannot add a library which targets .NET 4.x, they must rewrite and publish a new version/

Resources