I have gotten NH doing a little bit of Hello World and am moving on
to the next step. I found a tutorial on generating schema (*1 below).
He chooses to use a test tool to run the code for this process. Sounds
like a good idea, so I stuck it into mbUnit.
Here's the code in question:
Configuration config = new Configuration();
config.Configure();
var aaa = new SchemaExport(config);
When I step through, it dies on the config.Configuration() step (and I
note that it works just fine in the target project). I cannot get any
information about it from the debugger but my intuition tells me that
the new Configuration is not being created because of something about
the .cfg (which is, btw, in the test project directory just as it is
for the test target project).
My questions (in addition to, Do you see anything obvious that I
should have asked if I had half a brain?) are:
1) Is there any way to explicitly specify the path to the .cfg so that
I can be sure it is being found.
2) I specify the assembly in said .cfg. It is the one-word name of the
target project where all my data objects are. The assembly is
referenced and is visible to mbUnit for another test. Is that the
correct way to connect NH to the assembly.
3) Is there any way to get NH to tell me status/debugging info? Is
there any way to get it to simply verify its setup/cfg?
It's a good thing that all of you like NH so much. I would have lost
patience days ago. It is so difficult to get it going.
best,
tqii
*1:
http://blogs.hibernatingrhinos.com/nhibernate/archive/2008/04/28/create-and-update-database-schema.aspx
--
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en.
