This is an old post but thought I would weigh in since my company is still kicking it old school with XML component registration over installers. In our case we used partial assembly name for System.ServiceModel as the O.P. did here. For whatever reason, this consistently fails. Oddly, fuslogvw provides a warn instead of an error for this scenario. So moral of story is use fully qualified assembly name for System.ServiceModel when registering WCF components such as IServiceBehavior and IErrorHandler.
Ex: System.ServiceModel.Description.IServiceBehavior, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 "Many Bothans died to bring us this information." On Sunday, June 28, 2009 11:19:53 AM UTC-5, Uri Goldstein wrote: > > Hi, > > Might anyone know why the following exception is thrown when using the > WCf Integration Facility: > > "Could not load file or assembly 'System.ServiceModel' or one of its > dependencies. The system cannot find the file specified. " > > I'm not sure but I suspect this is related to my trying to inject an > IServiceBehavior with the facility. > > Only if I set CopyLocal=true on the reference to System.ServiceModel > in my project does the exception go away. I assume the DLL is in the > GAC so why couldn't the WCF Integration Facility find it? > > > Thanks, > urig -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/groups/opt_out.
