bll | 易学教程

C# .NET4.0 TableAdapter.Update() won't insert new record

阅读更多关于 C# .NET4.0 TableAdapter.Update() won't insert new record

问题 I have a small application which consists of a DAL, BLL and the Application itself all in different projects under one solution in Visual Studio 2010. My DAL is using an xsd file to query the database and my BLL has methods to get the information from the DAL and do stuff with it. Currently I am trying to insert a record using the code behind of the application to make a call to a method in the BLL which then attempts to insert the record by using the Tableadapter.Update() method generated in

BLL,DAL,BO,inserting data

阅读更多关于 BLL,DAL,BO,inserting data

问题 I need your advice. I am trying to develop a 3 layer architecture in ASP.NET that separates BBL,DAL,BOboj. Inside the DAL, I collect the data via _view. What I wonder, should I write another BOboj for every view??I have already has a BOboj class but it doesn't contain all fields. When inserting data, I have to use my BOboj,however, when listing, should I create BOboj_view class or another something ?? inserting data (My colum only contains those values) BOboj { private int _PId; private

How does the MVC pattern differ, if at all, from the DAL / BLL design pattern?

阅读更多关于 How does the MVC pattern differ, if at all, from the DAL / BLL design pattern?

问题 I'm making my way through the early Data Access Tutorials on Microsoft's ASP.NET website and it occurred to me that this all seems awfully similar to what I have read about separating your logic and presentation code using the MVC pattern. As a newbie I have yet to implement the MVC pattern but I'm curious as to how these two design structures differ and if I should be focusing my attention on one or the other, particularly in the context of web design. 回答1: The link you've posted for the

Linq to SQL Updating through BLL issues - Best Practices

阅读更多关于 Linq to SQL Updating through BLL issues - Best Practices

问题 The Setup: I have a large form with many fields that are collected to update a Product object. So in the ASPX page the user changes the fields that need updating and they hit submit. In the code behind I do something like this; Dim p as New MyCompany.Product() p = p.GetProductById(ProductID) I extend the Product partial class of Linq to SQL to add this method (GetProductById) to the object p.Name = txtName.Text p.SKU = txtSKU.Text p.Price = txtPrice.Text ... p.Update() This is an Update

DAL/BLL and Client/Server: Should the client use BLL or DAL objects for presentation? Or maybe another layer (data transfer object?)

阅读更多关于 DAL/BLL and Client/Server: Should the client use BLL or DAL objects for presentation? Or maybe another layer (data transfer object?)

问题 I'm writing a client/server system. The server has a DAL/BLL design. The client is responsible for presenting the data objects and providing dialogs and wizard to allow the user to update these objects (i.e. adding/editing a user). Initially I thought I'll just make the DAL objects have a universal data provider object so they can be used by the client as well as the server. For instance, when the data object is being used by the server, the database is the data provider; when the data object

n-layered architecture - BLL, DAL and interfaces. What is best practice?

阅读更多关于 n-layered architecture - BLL, DAL and interfaces. What is best practice?

问题 I have a question regarding n-layer architecture. I thought long and hard before asking this question as there's a lot of similar questions here already... however, after literally a day and a half looking at it and reading these other answers I'm still unsure. The variety of seemingly similar terminology and different approaches has me confused. If I had a BLL and a DAL in different class libraries, one way to communicate between the BLL and DAL would be to utilise an interface, kind of like

Communication between BLL and DAL

阅读更多关于 Communication between BLL and DAL

问题 Solution setup: DAL (class library) BLL (class library) Common (class library (some common functionality - enums, logging, exceptions,...)) Application1 (Windows Application) Application2 (Windows Application) WebApp (Web application) ... Let's say I have a Customer entity, which is: a table in SQL server a CustomerDataTable in DAL a Customer class in BLL a BLL.Customer class in all the applications What kind of objects should BLL and DAL use for communication - DataTable or List<Customer>

Help with debate on Separation of concerns (Data Access vs Business Logic) [closed]

阅读更多关于 Help with debate on Separation of concerns (Data Access vs Business Logic) [closed]

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 5 years ago . I had a debate with my co-worker on whether certain logic belongs in the data access or business logic layer. The scenario is, the BLL needs some data to work with. That data primarily lives in the database. We want to cache that data (using System.Runtime.Caching) so it's

Help with debate on Separation of concerns (Data Access vs Business Logic) [closed]

阅读更多关于 Help with debate on Separation of concerns (Data Access vs Business Logic) [closed]

Closed . This question is opinion-based . It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Closed 5 years ago . I had a debate with my co-worker on whether certain logic belongs in the data access or business logic layer. The scenario is, the BLL needs some data to work with. That data primarily lives in the database. We want to cache that data (using System.Runtime.Caching) so it's quickly available on subsequent requests. The architecture is such that the DAL and the BLL live on the

BLL,DAL,BO,inserting data

阅读更多关于 BLL,DAL,BO,inserting data

I need your advice. I am trying to develop a 3 layer architecture in ASP.NET that separates BBL,DAL,BOboj. Inside the DAL, I collect the data via _view. What I wonder, should I write another BOboj for every view??I have already has a BOboj class but it doesn't contain all fields. When inserting data, I have to use my BOboj,however, when listing, should I create BOboj_view class or another something ?? inserting data (My colum only contains those values) BOboj { private int _PId; private string _Name; private int _ClassId; } listing data BOboj_view { private int _PId; private string _Name;