Yes thats what i did,
as stated in the first post
Code:
[JoinedSubclass(Extends = "Namespace.BaseClass, MyExecutingAssembly")]
[Key(Column = "Id")]
The baseclass is specified with the Fullname and the Assembly it resides in.
Mapping.Attributes then generates the hbm.xml files and adds
the Fullname and Assembly of the subclass which is retrieved reflectively.
I checked them as well in
Code:
HbmSerializer.Default.Serialize(Assembly.LoadFile(@"c:\Library.dll"), "Library.hbm.xml");
they are correct alltogether.
Maybe it has something todo with the location of the assembly since i lazily copied it to c: in order to simulate the module behaviour
My proposal, i'll create a test project which reproduces the behaviour and post it somewhere on the net
- will check for myself by debugging it and try to find out what is happening. i currently only use the binary nhibernate dll
thanks, regards Klaus