I want to upgrade to NHibernate 2.0 from NHibernate 1.1.
Am I obliged to upgrade Spring.NET to v1.2 as well since we're using the NHibernate/Spring.NET integration module? We're currently publishing our releases under .NET Framework 3.0.
I did this a few months ago and didn't have any major issues. I think I had to make a couple of changes to a few relevant calls, and use the NHibernate20 assembly. Give it a go, what harm is it going to do? As long as your code is in source control you should be able to revert back. And then you can run your tests ;-)
.NET Framework 3.0 or 3.5 is okay as well, as they both sit on top of .net 2.0: http://en.wikipedia.org/wiki/File:DotNet.svg
Good luck.
Related
I'm trying to change ASP.NET Core web application with .NET Framework as a target framework to use .NET Core 3.1.X
I try changing the target framework in the project file (.csproj), I encounter dependency issues, dependency conflict....
Is there any straightforward method to solve this issue?
Before you start your migration, you should know there’s several difference between .net framework and .net core, so please follow the official document to do some Pre-Migration steps.
Then you can follow this official document to migrate your application from framework to .net core 3.1.
Since your ideal .net core version is 3.1, still I suggest you can try to use .net 6. Also, you can use this upgrade tool to reach your goal. In fact, using this upgrade assistant is a batter choice than you doing it by yourself. Even if you are insisting using .net core 3.1, you can use this assistant to upgrade your version to 6 first then change it to 3.1.
Note:
Before you start your migration, please make a backup of your original project. That's because some packages in .net framework may be no longer available in .net core. So if there're some errors occur, you can go back to the original one.
I am getting a little confused by all the naming and versioning of .NET. I think I understand the whole .NET Framework / Standard / Core thing, but I am now moving into ASP.NET Core territory (I want to give my console application a web interface with Kestrel).
When using the NuGET package manager, I can see the Microsoft.AspNetCore.Hosting package, needed to run the webserver. But the highest available version is 2.2.7.
Question now, is that 2.2.7 part of ASP.NET Core 5.0, or do I have some configuration incorrect that I do not get the latest version for my application?
And if it is indeed part of ASP.NET Core 5.0, where can I find that reference? This table helped me a lot with understanding the core libraries.
I assume you wanna this document which tells about your package :
https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.hosting?view=aspnetcore-5.0
And I think you can focus on those classes or interfaces you'll use and take a look if those are supporting .net 5 by click and refer to the details page. You'll see Applies to at the bottom of each page such as this one.
If I misunderstood in some place which made my post isn't suitable to display here, pls point it out and I'll delete it.
I have a custom authentication component that is working with net core 2.2. I've started migrating the project to net core 3, but it seems like MS hasn't updated the authentication Nuget packages.
Until now, I was referencing the Microsoft.AspNetCore.Authentication package. The package still exists, but hasn't been updated to net core 3.0 (it's still on the 2.2 version).
I can't keep using it because net core 3.0 has moved the RequestPathBaseCookieBuilder type to a different namespace (so, at runtime, I'll get a tyoe loading exception). A quick search shows that only the Microsoft.AspNetCore.Authentication.OpenIdConnect has been updated to net core 3.0 (and if I add it to my project, then my component to work without any issues).
Anyone knows why MS hasn't still updated the other security nuget packages to version 3? Is there anyway to solve this without using the openidconnect nuget package (I'm only using it because it was the first that was updated and it will bring the correct Microsoft.AspNetCore.Authentication assembly that I need for my project)?
Looks like I was 10 minutes too late, but you posted the answer as a comment, rather than an answer, and I like questions having answers so I stop opening them when browsing the question search results.
Anyway, as you discovered, .NET Core 3.0 no longer uses packages for base class libraries (BCLs). Instead, they're just part of the SDK, so by targeting netcoreapp3.0 or netstandard2.1, all BCLs are just available. This should eliminate a lot of problems that earlier .NET Core projects had, particularly when referencing .NET Standard 1.x assemblies from netcoreapp2.x tfms. Although the largest benefit will be when all referenced packages target netstandard2.1 or netcoreapp3.0 or above.
Ok, so finally got it. The solution is to use the FrameworkReference element with the Microsoft.AspNetCore.App meta package.
Googled a bit but couldn't find the .Net standard version for .Net core 2.2. Only version I got is,
Any hint please?
As you can see in the table you have uploaded, .NET Standard 2.0 is the latest available and it is fully supported by .NET Core v2.0. As you can see in this release doc. section, .NET Standard 2.1 will be supporting .NET Core 3.0 and also .NET Core 2.2. For the whole page check here.
In my opinion, you can go with .NET Standard 2.0 if you do not deal with extreme things (I mean recently added parts of .NET Core). This can yield some errors but still worth the try.
I'm trying to convert quite big project from .net 3.5 to .net 4.0 and we have wwf 3.5 in it. Googling this question i realized that i would need to rewrite workflow almost from scratch. so my question is , if i can use .net 3.5 workflow in .net 4.0 project ?
Yes, you can. WF4 doesn't replace WF3. They are in different namespaces. The blog post isn't on topic, but the blogger is and he states this fact.
As Will said, the WF3 stack is still present and supported in .NET 4 so you don't have to migrate your workflows to WF4. That said all future efforts will go towards WF4 so sooner or later you will probably have to bite the bullet. For now you don't have to though.