# Friday, January 04, 2008
« Mmmm Podcasts | Main | Setting the ASP.NET Session Store Connec... »

For 15 minutes today I couldn't figure out why my Windsor configuration was blowing up with a mysterious and unrevealing error: "deserialize element cannot process element component."  This happened after I moved some configuration out of my main windor config to a new embedded resource config file. I thought is this a bug in Windsor?  After briefly looking through the Windsor test source it was pretty obvious that this is supported and tested.

It turns out that I forgot to include the "components" tag in my config file.  Argh!  The answer was right in front of me all this time, I just didn't see it - even after comparing my broken config to a working config.  I'm glad I'm not the only one to have this problem...

Thursday, July 31, 2008 1:32:12 PM (GMT Standard Time, UTC+00:00)
Thanks ;)

best regards,
Flo
Flo
Monday, February 09, 2009 7:14:48 PM (GMT Standard Time, UTC+00:00)
+1 After moving a subset of components from one config file to the next I forgot the "components" tag too. Thanks for sharing:)
Name
E-mail
(will show your gravatar icon)
Home page

Comment (Some html is allowed: a@href@title, strike) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

Enter the code shown (prevents robots):

Live Comment Preview