A few year ago, we developed a large ASP.Net application (C# / .net 3.5) that had to be \"Database Engine\" non-dependent (meaning this application could either use SQL Server, Oracle, MySQL ... as DB
There\'s this web app, which relies on a sort of data access library (simple data objects and associated objects to perform CRUD operations on them) which is generateddirectly from the database.
What are the recommended considerations to design Data Access Layer for Enterprise level application. Application built in asp.net 2.0 and N-Hibernate is used in DAL, but there are many flaws in curre
I would like to understand a few basics about Assemblies and Namespaces. I\'ve reproduced an NHibernate tutorial, and everythin开发者_运维技巧g works fine. But I\'m not sure if I agree on what classes
// Add into DB int recordID = 0; using (tblArtworkTemplatesTableAdapter tblAdapter = new tblArtworkTemplatesTableAdapter())
I\'ve created a DLL in Visual Studio that holds my Entity Framework ObjectContext. I\'m trying to access its various ObjectSets from PowerShell.I\'m doing this because I have some XML files that I\'m
Below is a method from from my console application calling a DAL method. Whats the best way to wrap this in a BLL method so it can be called directly from the presentation? I have worked on projects i
Just a quick question about my Domain Layer/ Domain Service... Should I allow this layer to have read only access to the database? i.e. hook up a IReadOnlySession and only allow the Repository Layer t
I\'m trying to write a small app with very strict boundaries between BLL and DAL and am now wondering what the best way would be to pass the data (Domain Transfer Objects) between the layers.
I am working on a large project where I have to present efficient way for a user to enter data into a form.