I upgraded my application from Abp 0.9.7 to 1.0
Now, when the method Application_Start of the class AbpWebApplication is called I get the following error
[ComponentNotFoundException: No component for supporting the service Abp.Web.Configuration.IAbpWebLocalizationConfiguration was found] Castle.MicroKernel.DefaultKernel.Castle.MicroKernel.IKernelInternal.Resolve(Type service, IDictionary arguments, IReleasePolicy policy) +120 Castle.Windsor.WindsorContainer.Resolve() +68 Abp.Web.AbpWebApplication`1.Application_Start(Object sender, EventArgs e) in D:\Halil\GitHub\aspnetboilerplate\src\Abp.Web\Web\AbpWebApplication.cs:37
I don't plan to use Abp language management because I have it already solved using other libraries and javascript code. What should I do to avoid this problem and bypass Abp language management?
3 Answer(s)
-
0
Hi,
Can you check again that all Abp related nuget packages are updated to 1.0. There might be some old dlls in the bin directory.
You can disable abp localization like this in the PreInitialize of your web module.
Configuration.Localization.IsEnabled = false; -
0
Thanks for the reply.
After cleaning all assemblies, and referencing again it works as expected.
Just a comment on using Configuration.Localization.IsEnabled = false. Even if you set to false it still has effect on the thread culture. I had to put the following code on my application, to avoid Abp overriding my culture settings (which is as <globalization uiCulture="en-US" culture="en-US" /> in the web.config)
protected override void Application_BeginRequest(object sender, EventArgs e) { var currentCulture = System.Threading.Thread.CurrentThread.CurrentCulture; base.Application_BeginRequest(sender, e); System.Threading.Thread.CurrentThread.CurrentCulture = currentCulture; System.Threading.Thread.CurrentThread.CurrentUICulture = currentCulture; } -
0
You are right, Configuration.Localization.IsEnabled = false does not do anything about current thread culture.
