Andrus,
Have you looked at the documentation for the ActiveRecordStarter class
in the Castle documentation? There ^should^ be something there (I'm
assuming that a framework has some documentation).

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> second line in my application is
>
[quoted text clipped - 42 lines]
>>>
>>> Andrus
Andrus - 15 Oct 2007 10:00 GMT
Nicholas,
ActiveRecord dynamically builds an NHibernate mapping definition.
Part of that NHibernate mapping is the type information. It's expressed in
the usual .NET manner:
fully.qualified.typename, assemblyname
What's happening is that ActiveRecord is building up a mapping for one of
types inside ModelEntity.DLL and defining it like this:
"Namespace.ModelEntity.ClassName, ModelEntity"
(this is assuming "ModelEntity" is the name of the assembly). As you can
see, there's no path information in there (by definition) so I'm guessing
when this information is passed to NHibernate, it loads some information
using the fully qualified type information above and then normal .NET rules
for locating assemblies happens (current directory, then probing paths).
How to force .NET to search c:\temp directory first for assemblies ?
Andrus.
> Have you looked at the documentation for the ActiveRecordStarter class
> in the Castle documentation? There ^should^ be something there (I'm
[quoted text clipped - 46 lines]
>>>>
>>>> Andrus