we have a saga that calls numerous handlers. I want to start the migration from 2.6 to 4.0 so I have upgraded one of the handlers to 4.0. If I deploy this handler alongside the other 2.6 handlers and with a 2.6 saga that calls both types of handlers is there going to be trouble? Is this even possible?
Thanks
take a look at the NServiceBus 4.0 release notes
it states that 4.x is not compatible with 2.x...
upgrading to 3.x and then 4.x seems like a less painful option
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 building an app that uses .NET Framework 4.5. One of the controls that I'm using is being flagged as an accessibility issue. That issue was fixed in .NET Framework 4.7.1, but I can't target a newer version now. Is there a workaround for this?
If you are unable to update your .NET Framework but want to take advantage of the accessibility improvements in the later versions, you can use Accessibility Switches to "configure your app to opt into accessibility features if it targets .NET Framework 4.7 or an earlier version but is running on .NET Framework 4.7.1 or later."
I have a .Net Core 3.1 web application. Since I have to communicate to a legacy service using .Net Remoting, I decided to change the TargetFramework to 4.61. This has caused error with (IApplicationBuilder)app.UseHSTS(). So, I updated my referenced version of Microsoft.AspNetCore.SpaServices.Extension to 2.2.0. However, UseHSTS is not available with it. Is there an alternative solution?
I would like to write Microsoft event log in my application using Asp.net core 1.1. I have searched and got the extension "Microsoft.Extensions.Logging.EventLog". But I am unable to install on my application due to compatibility.
Is there any other possible solution to achieve event log in asp.net core 1.1?
Thanks in advance.
The compatibility problem you hit likely appears because you attempted to install the 2.0.0 version of Microsoft.Extensions.Logging.EventLog for your ASP.NET Core 1.1 application.
In preparation for the final release of ASP.NET Core 2.0, it appears that the NuGet packages were published early, which makes those the newest stable versions on NuGet causing the NuGet package manager in Visual Studio to pick those by default.
You have to be careful with which versions you pick when installing dependencies for ASP.NET Core. Especially soon, when 2.0 releases, you have to make sure to always pick the latest 1.x release for as long as you stay on ASP.NET Core 1.x.
In your case, you need version 1.1.2 of Microsoft.Extensions.Logging.EventLog which is the latest 1.x version for the dependency. So either pick that in the NuGet package manager, or change your .csproj to include the proper version:
<PackageReference Name="Microsoft.Extensions.Logging.EventLog" Version="1.1.2" />
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.