we are trying to migrate to .net-core 3.0 from .net-core 2.2, is nhibernate fully compatible with .netcore 3.0 ?
Currently, we are using .netcore 2.2 and nhibernate is fully compatible.
As I know Nhibernate 5.2.3 is full compatible with .net core 3.0.
It seems Nhibernate 5.2.6 is same as 5.2.6.
https://gunnarpeipman.com/aspnet-core-nhibernate/
BR
Related
I am solution architect. I need to upgrade my application from .net 2.0 to .net 4.7
What will be the roadmap for that there is no change code or architecture of application
I have Windows server 10 ready it comes with .net 4.5 or higher.
What should I do with IIS ?
Does that needs to be changed to ?
What are the other steps to follow?
Thank you
Suji
I have a VB.NET Windows Forms project targeting the .NET Framework 4.7.2:
I am trying to install Microsoft.EntityFrameworkCore.SqlServer of which the latest stable version is 5.0.8:
However after clicking install and accepting all terms I get an error:
Could not install package 'Microsoft.EntityFrameworkCore.SqlServer 5.0.8'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Does anyone know what the heck its moaning about version for?
Does anyone know what the heck its moaning about version for?
EF Core 5 requires .NET Standard 2.1. .NET Framework only supports .NET Standard 2.0. So it will never work.
EF Core 3.1 is the last version to support .NET Standard 2.0, and so it's the last version of EF Core compatible with .NET Framework.
But .NET Core 5 supports Windows Forms.
So the options are:
upgrade everything to .NET Core 5
downgrade EF Core to version 3.1
switch from EF Core to EF 6, which is mature, stable and supports .NET Framework
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.
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.
I want to create an application using AjaxAjaxControlToolKit in ASP.Net 2.0
How to use AjaxControlToolKit with ASP.Net 2.0
http://ajaxcontroltoolkit.codeplex.com/releases/view/11121
This version should work for .NET 2.0