Architecture :: Should Multiple Project Be Used For UI / BLL And DAL
Feb 12, 2010
I have been creating my BLL and DAL with in the same project as my UI. These have been logical tiers in their own folder with in the same project, that's with in the same solution. I want to try to create a solution that is more like a truly multi tiered app.
I've heard people talk about using a separate projects for their DAL and BLL. My understanding is that these would be separate dlls that would contain the appropriate code for each of the these tiers. I have a few questions regarding this.
Is this a good way to do this? It seems like a logical approach. It also seems like the next step in me moving towards an architecture that's truly tiered. Should I do this differently?
Should the projects for the BLL and the DAL use the same namespace? I think I read that some people use a namespace for each of these that indicates what they are, such as BLL and DAL.
i know some thing about the MVP pattern... but when you want to develop a project(web project) based on the MVP pattern from where we need to start... i mean which component we need to start developing first ... Model or View or Presenter... what are the points that we need to keep in mind....
When implementing MVP in a ASP.NET project, what are your preferences for how you organize the relationship between your presentation project and your web project?
I am trying to use Domain Driven Development (DDD) for my new ASP.NET MVC2 project with Entity Framework 4. After doing some research I came up with the following layer conventions with each layer in its own class project:
[code]... Currently my Repositories layer holds a reference to the Domain layer.From my understanding injecting a UserRepository to the UserService class works very well with unit testing as we can pass in fake user repositories.So with this architecture it looks like my Web project needs to have a references to both my Domain and Repositories layers.But is this a valid?Because historically the presentation layer only had a reference to the Business Logic layer.
We have a web solution. In it we have 2 websites and a core project in the core project are some classes that encapsulate data that a database utility class searches using sql and populates the entities. The entities are stored in generic lists.
We have just upgraded our project and I want to start using linq, I was wondering the best way to go about it. SHould I creata new linq project? Or Should I just use ling on new pages only and stick to our current data access layer for pags that already exist?
Its vital that we start using linq as it will save us time in the future
I am using asp.net 3.5 and I am trying to create a project structure (asp.net web solution with UI/Business/Data access) which would be like a base and ready for any new projects in my team and all could use this standard structure only as a base(outer boundary) and they can expand the structure. Also adding on to it I wanted to include certain features like adding libraries of reusable code/functions, so that every team member could use functions from my library within this base structure. To summarize the above, I need to create standard .net project structure/framework/architecture with resusable code library included in it. How can I do this..
I am working on singleton desing patterns and want some real world example of design patterns.Can you please give me an example how you have used singleton pattern in you project. I would appreciate if you can provide code.
i ma new to asp.net, i am just learning asp.net using this site and some resources from internet , internet is the only source for me. and here i have a project that should be designed by the patter of 3 tier architecture. i have an idea, but i couldn't start it, need your guidance, if i did this , it will very useful for me to get a job.these are the requirements and steps.
I am not new to ASP.Net application development but I haven't used some of the new frameworks or features that are used in applications these days.
For cross-cutting concerns, things like: Logging, Caching and DAAB are used in projects these days to implement proven and efficient source code from either Microsoft or other third party vendors such as Log4Net for logging purposes.
I'm about to begin a new asp.net application using .net 4.0. Only concern I have is since the project calls for reporting, I cannot use SSRS with SQL Server 2008 b/c the tempate for Bus Intelligence Projects is missing from 4.0. I've been told that the next release of SQL Server 2011 (some time this year), will resolve this problem. Meanwhile, I'm wondering if the following approach would work:
1) Create the application in VS2010 using the SQL Server 2008 db.
2) Create the SSRS Bus Intelligence project using VS2008 and create a seperate website pointing to the same SQL Server 2008 Db?
Kind of a hack, but I guess the only problem with this is, the Bus Intelligence project will not be able to reference and leverage and DLL or code from the application.
how to design following small webproject and database .i am totally new in this area.
I need to quickly develop a system so that everyone can access the status of the job going online into the system
Activities
Move the job between work centers when it's completed.
Transfer button. So when design is done we should be able to click the transfer button and move the job from Design to Procurement
Here are the work centers.
plan cerement TST Shipped Each work center should have due dates User will have to update manually due date for each work center and this will be different for each job.
I'm going to have to write a big system in January with ASP.NET MVC3 / C#, and need to know how to write a system that will WORK. I do have a bit of experience with ASP.NET MVC and C# but would not call myself an expert. It needs to be extensible so that I can extend it later with new features. How would one go about this? Is there books that explains this topic in detail or should I use trial and error? In short I need to know good design practice in my code thats extend-able for the future.
I have two projects (Project A and Project B), these projects are hosted in different locations and on different servers. Project B want to access the files of Project A. which technique is required to fulfill my requirements.
When i create a new class on data layer,i can access that on business layer by creating object of that class.
but when i create a new "public class" on business layer i cant access that on presentation layer.
another thing is, after building business layer if copy Business.dll,Business.pdb,Data.dll and Data.pdb from business layer to presentation layer "BIN" i can access that class
I have a page in a structure as follows. But the loading time of the page is takes 20 or more seconds. In usercontrols i'd used Telerik RadControls, for that reason i can't use updatepanel to avoid script problems or etc. I had tried to add usercontrols dynamically but there is about 14 usercontrols and it takes the same time period :(. I had tried using PartialUpdatePanel as in [URL] but it's not compatible with telerik controls. My client wants to have the all 14 usercontrols being in the same page (not divided by tabs or wizards)
Structure :
MasterPage Page 14 Usercontrols that contains RadListViews has couple postback events.
I am supposed to develop an enterprise-class ASP.NET Web Application that connects to multiple databases. For example when the web form loads, I should populate different ASP.NET controls (GridView, DataPager, TextBox, DropdownList etc) from multiple databases (SQL Server, Oracle, DB2, SAP Server etc) and also, edit the data in the controls and save the data to the respective databases on button submit.
Should I use Web Service or WCF for data integration, if so is there a limit on the size of the data?
What should be the architecture considering the application should be scalable and easy to maintain?
I recently received a project that contains multiple web applications with no MVC structure. For starters I've created a library (DLL) that will contain the main Business Logic. The problem is with Caching - If I use the current web context cache object than I might end up with duplicate caching (as the web context will be different for every application).
I'm currently thinking about implementing a simple caching mechanism with a singleton pattern that will allow the different web sites (aka different application domains) to share their "caching wisdom". I'd like to know what is the best way to solve this problem.
My requirement is i need to display some quotes from some vendors in my User Interface. Some of the quote details will be fetched from database where as some vendors are giving web services to get the quote results. I need to combine the quotes from database as well as the various web service response and display in the grid.
We need to download multiple files from remote servers. It is a process that would take few hours to complete, since we are talking about images ~50kb each and more than 250.000 in total. Each images will downloaded, resized and then imported to SQL.DB, so we do not need to write files to the disk. Also the applications need to use network credentials, since it is behind ISA.
From your experience, what is the best method to implement this? Should we use WebClient or HttpSockets? Should we use Async methods or Threads ? How can we implement for example 5 simultaneously download to achieve better speed, since we may getting files from many different servers at once?
I have a form which allows users to modify data, what's the best way to handle that so if two or more users try to make an update i get the data in there properly without overriding the new stuff. for example if name and bday are in the form, user1 changes name but not bday, same time user2 accesses the form, the original name and bday are there, user1 saves, but when user2 saves, since he had the original name value the original is saved over the first.
I'm working on a webforms aspx app (not MVC) and I'm not sure if I should just create separate pages or somehow make multiple views on the same aspx page for the following scenario: Basically, I need to give the user the option to view a set of data a few different ways (essentially different group by's from a data perspective)... the data is always the same, its just a matter of how to arrange on the page...
each way I need to present the data will essentially consist of 2 repeaters, one nested inside the other. The outer repeater will display a nice header section with the nested repeater showing the list of items under that heading. view by book title (title is outer repeater, with the book list being the nested repeater, yes, multiple books with same title for this example - the app has nothing to do with books, this is just to illustrate)
Book Title: A Good Story Author - Publisher - ISBN Dan Johnson - Smith Publishing - kjdkjfd99898989 Susan Day - Smith Publishing - aa777fd99ff Greg Greger - Corp XYZ - amkj897hgrt554
Book Title: Another Good Story Author - Publisher - ISBN Frank Franky - Corp XYZ - kj3kjfd9d9980 Jason Cambel - Smith Publishing - 7g7fddddttt Jill Breker - Smith Publishing - d9ddt523321
Or, view books by publisher (here the publisher would be the outer repeater and the list, with different fields compared to first view, is the nested repeater.
Publisher: Smith Publishing Title - Author - ISBN A Good Story - Dan Johnson - kjdkjfd99898989 A Good Story - Susan Day - aa777fd99ff Another Good Story - Jason Cambel - 7g7fddddttt Another Good Story - Jill Breker - d9ddt523321
Publisher: Corp XYZ Title - Author - ISBN A Good Story - Greg Greger - amkj897hgrt554 Another Good Story - Frank Franky - kj3kjfd9d9980
so what do I do here? Just making separate pages is simple and would work, but is there something else I should be considering? There will be 3 different views, so 3 pages total if I went that route. Something is making me think I should be doing this all within one aspx page? maybe just toggling the visible property of the repeater controls? but then I was thinking each of these repeater controls is databound, and I assume even if they are not visible they still incurred database hits to get the data, right? and that could be bad?
I have a website hosted with sql 2008 database on Godaddy. Here's my problem descriptionbefore I actually begin implementing.Entries are made in a table named "XYZ" by a third party program. Now, there are multipleclients (could be asp.net ajax web based or vb.net desktop clients which I have not decided yet) who read data from this "XYZ" table every 10-15 seconds. The connection string used by these clients would be same. If I have 10000-20000 clients making connections and querying same table, would that cause any breakdown? Since my connection string is same, connection pooling isautomatically in place.
What else do you think I need to take care of? Or is there any better way to implement this setup?Also, should I go for asp.net ajax client implementation or vb.net(c#) client implemtation ?Your inputs would be highly helpful to me. I am looking for a medium to long term solution to thissetup.
