As you know NHibernate 3.2 has native bytecode provider, which has some breaking changes with castle bytecode provider.
For example:
public class SomeEntity
{
public virtual string SomeProperty { get; **private set;**}
}
Is working fine with NHibernate 3.1 and Castle Bytecode provider. And not in NH 3.2.
I'm using nuget for managing my dependencies and do not want to manage them by hands. So my question is: would bytecode providers for castle, linfu and spring be available in nuget?
The NHibernate team won't support those bytecode providers any more.
It hasn't been officially voted, but I don't think the Castle team will support it either.
Fortunately, this is all open source, so you can just go ahead and grab the code and maintain it and put it on NuGet. It could be either a NHibernate contrib or a Castle contrib project.
Still, if this used to work and doesn't anymore (and the change isn't documented, make sure it isn't), it could be a regression bug, and so it should be reported (make sure it hasn't been reported already) and fixed.
NHibernate 3.2 has introduced quite a number of undocumented breaking changes, particularly for those folks previously using the Castle bytecode provider.
The Castle bytecode provider is being maintained on GitHub, in this repository: https://github.com/sibartlett/NHibernate.ByteCode
来源：https://stackoverflow.com/questions/7052273/will-castle-bytecode-provider-for-nhibernate-3-2-ga-be-available-in-nuget