I'm gonna guess that there's a XmlSerializer in there somewhere. The Serializer makes a guess at the assembly early in the process before it has all the information. The exception should be caught and ignored internally, but you will see it if you have "break on Exceptions" turned on.
On Wed, Sep 9, 2009 at 11:19 AM, Jan Limpens <[email protected]> wrote: > Hello, > > I am getting a few of those recently: > Exception: Could not load type 'FestaExpress.Web.Settings. > ShopConfigDictionaryAdapter' from assembly > 'FestaExpress.Web.FestaExpress.Web.Settings.IShopConfig.DictionaryAdapter, > Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'. > This assembly does not exist, it should be FestaExpress.Web. > (FestaExpress.Web.Settings.ShopConfigDictionaryAdapter does not either, but > I guess this is DynamicProxy speaking) > > some code: > > protected IShopConfig Configuration > { > get > { > if (configuration == null) > configuration = GetSettingsFromWebConfig<IShopConfig>(); > return configuration; > } > } > > public T GetSettingsFromWebConfig<T>() > { > return > DictionaryAdapterFactory.GetAdapter<T>(ConfigurationManager.AppSettings); > } > > any ideas? > > -- > Jan > > > > -- Truth, James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
