I was using version 0.9.7 and .Net dictionaries were serialized as follows in json {"key1":"value1","key2":"value2"}
Now dictionaries are serialized as: {"Comparer":{},"Count":2,"Keys":["key1","key2"],"Values":["value1","value2"]}
Any idea how can I change serialization settings to get the 0.9.7 behavior? I have a lot of javascript code that relies on the previous structure.
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?
All my assemblies are strongly-named, so when I try to use the Abp assemblies in my project I get the error "Could not load file or assembly 'Abp, Version=0.8.4.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required"
Is there a Nuget Package version of the assemblies that are signed/strongly-named?
The only option that I have now is to do not sign my assemblies, but I would like to keep some benefits of signed assemblies such as making harder assembly tampering or substitution.
