Hi Fokes: I'm currently working on an application which is using NHibernate for some of it's data access. I have a bunch of clases that write to a database. I've currently set up a façade class to hide all details of data access-saving/loading etc. Is this the best design for multiple classes, I don't really want to go down the repository route, as only 3 database tables are being hit-the table being hit depends on the entity passed in to the save method as this is saved as xml and I'd ideally like to hold the session factory somewhere, the library is used in both sharepoint webparts and a console application. Any ideas greatfully accepted, as it seems my design is convoluted, I carn't see where though Cheers Sean.
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
