This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 43%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
I am upgrading my current project from .NET Core 3.1 to .NET 6.0. After upgrade of project along with its dependencies, I am getting below error. I have tried to investigate but no luck.
Please help.
This project uses
Thanks,
Pavan.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Pavan Kumar ,
After upgrade the target framework and referenced packages, you may need to delete the bin and obj folders. Run dotnet nuget locals --clear all to clear the NuGet package cache.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Are you using SimpleInjector by chance? It sounds like you have a dependency on a package that references an older version of the MVC libraries and that older version is getting pulled in instead of the current version. Firstly ensure all your packages are updated. Then check the output directory for your app and ensure the version of the MVC assembly is 6.0.
I have tried commenting below code AddWindsor() service method which used for DI in my project, after that I am able to run my project but without few services not working property as expected. So, it might be using older version other than 6.0.
But still I need below code to be added for my service collection.
services.AddWindsor(container,
opts => opts.UseEntryAssembly(typeof(LoginController).Assembly), // <- Recommended
() => services.BuildServiceProvider(validateScopes: false));
But, its causing an exception as specified earlier.
As I mentioned in my answer, that would mean the version of the MVC assembly that is getting dropped into your project's output directory is likely the older version of the library. Please confirm that the version of the MVC assembly is 6.0. Also it seems like your version of Castle is old as well. Please ensure you upgrade all your NuGet packages (using the solution level Manage NuGet packages) to their latest version. Mixing old and new versions is going to cause problems. You need to be running the version of the packages that work against the version of the framework you are targeting.
I have understood by Castle.Windsor documentation, it does not support .Net 6.0, will you suggest any DI framework alternative to Castle.Windsor that supports .NET 6.0 and upgradable on future releases for .NET?
.NET 5+ ships with its own DI so you don't need a custom library anymore if all you need is basic DI. See here. Note that the docs talk about ASP.NET but it applies to any .NET app.
Castle Windsor does support .NET 5+. What portions of its DI work well I cannot answer but the Nuget packages support newer versions. In general if you want to use a third party DI container (because most have more advanced features then what ships with the standard DI library in .NET) then you will need to link the third party library with .NET so the existing .NET components will work. Each library documents how to integrate with the .NET DI container.
Other libraries to choose from are many but you could try Autofac. That is the only additional library I have experience with. However I think you should just start with the built in DI support and only worry about an external library if you run into limitations. Keep the dependencies down is my view.
Thanks a lot for your response, I was able to replace the Castle with built in DI of .NET 6.0. Appreciate your help.