> I'm glad you've found the book useful, but that's really a poor example of
> an NHibernate configuration. The one from the book is a simpler. damn readers doing dumb things. ;-) I've been using NH for about 6 months with SQL server and now Oracle. I've found the config area one of the most difficult, error prone, and frustrating aspects. Often I'm stealing code from books or posts without really understanding how or why it works. In this case, I converted my xml stuff to code because I'm trying to hide this crud behind an API. I appreciate you telling me this stuff isn't needed - I'll delete it now (it came from some code I copied). > Of course, you have to feed it a database connection string, though I prefer to leave this in the app.config and specify only a connection string name in code. yup .. I just did that for the post. BTW, unlike many other users, I don't like XML config files - I view them as just another kind of source code except that they are not type safe, not checked by the compiler, and error prone. Once its deployed, the only thing that might change is the connection string, and I pass that in to the program. Regarding books, allow me to praise NHibernate in Action - one of the best technical books I've ever read. With these two resources, even a database novice like me can make this work! - lee -- 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.
