Oh, I'm not certain it's even being caused by Windsor. We have a fairly complex app with a lot of moving parts.
During the process of figuring out how we wanted to package it up for nuget, we started running into issues where the 2.5.3 nuget package would somehow end up asCastle.Windsor.dll version 2.5.1 when it was installed by our package. We're upgrading to 2.5.4 to see if that resolves it because the app makes fairly extensive use of type forwarding and it's not a clean upgrade to 3.x. While that's going on, I'm looking into what other issues we might run into if we decided to just ditch 2.5.x and make the switch. 2012/2/10 Krzysztof Koźmic <[email protected]> > what assembly versioning issue? > > @K > > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to castle-project-users@** > googlegroups.com <[email protected]>. > To unsubscribe from this group, send email to castle-project-users+** > [email protected]<castle-project-users%[email protected]> > . > For more options, visit this group at http://groups.google.com/** > group/castle-project-users?hl=**en<http://groups.google.com/group/castle-project-users?hl=en> > . > > -- 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.
