Hi. I don't understand something... We have worked to remove the very ugly cross reference between NHibernate and Castle.
For example you can use NH2.1 with the new Castle.DynamicProxy2.2 only by recompiling its bytecode. This feature is even used in Castle where the new coming soon ActiveRecord release will be release based on NH2.1 and its own Bytecode with the coming soon DP2.2; the same happen in Spring. What we have thrown out from the door now was reintroduced from the window. I don't know, and I don't want know, why Remotion is needing Castle.DynamicProxy but, IMO, we can't release NH3.0 with this new strongly reference to Remotion if it mean strongly reference to anything else than .NET and, as very most, log4net (NOTE: we are going to remove even the reference to log4net). If Remotion is really needed there is no problem but we need to talk with them to find a way to remove the dependency to Castle before release the first Alpha of NH3.0. -- Fabio Maulo
