I have spent the past two weeks doing research on the best implementation for a school project. We are creating a Calendar/ ToDoList/Academics tracker customized to our institution. We chose to make a C# WinForms application using NHibernate to maintain persistency with a database.
We are having trouble implementing a 3 tiered application and getting confused using OOP vs. Repositories. Currently, after authentication, the database is queried and a static User object is created which contains a list of groups, events, and tasks. However, when I try to display the items in separate GUI forms, the references are null. I think this is related to lazy loading, but I don't know. I have a feeling that my static user object is not the right idea. I am starting to think to not maintain any stale objects, and to use a repository for each display and use Refresh() to keep the data persistent. Am I on the right track with this thinking? Where do I store the authenticated user information? And how to I pass that to each repository to only retrieve data pertinent to the user? Any guidance you all could provide would greatly help a struggling student. Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
