You searched for the word(s): userid:809046

More Search Options

RSS Available

• Re: Publishing Website

  You can have the "marged" assembly deployment, as mentioned in the first link above.

  Posted to Configuration and Deployment (Forum) by joycsharp on 1/9/2009

• Re: Debate: Do We Really Need Three Layer Architecture?

  @EntitySpaces @TATWORTH @LudovicoVan Agreed

  Posted to Architecture (Forum) by joycsharp on 11/11/2008

• Re: Debate: Do We Really Need Three Layer Architecture?

  [quote user="joycsharp"] Now we need to consider whether we need to consider Tight or Loose Intimacy between Layers. For instance we have two data/business entities: School and Student, where we have some business rule included in School entity, where as vthe Student entity doesn’t have. For a “Tightly Intimate Layered” model, we may have SchoolBLL, StudentBLL at business logic layer, following which we’ll have SchoolDAL and StudentDAL at data access layer. For a “Loosely Intimate Layered

  Posted to Architecture (Forum) by joycsharp on 11/7/2008

• Re: Debate: Do We Really Need Three Layer Architecture?

  Thanks all of have such valuable opinions. However, I am in favor of using UI, Business Layer and Data Access Layer, for the entities which includes Business Rules. And it is not arguable that having this separation of concern will greatly help to increase the testability, maintainability and so on. Now we need to consider whether we need to consider Tight or Loose Intimacy between Layers. For instance we have two data/business entities: School and Student, where we have some business rule included

  Posted to Architecture (Forum) by joycsharp on 11/5/2008
  Filed under: layered architecture

• Re: Debate: Do We Really Need Three Layer Architecture?

  So far, few replies include the reality that we can’t really ignore the possibility of having new database vendor in future. Well, first it happens really rare to switch from one database vendor to another, and I guess 95%+ ASP.NET applications are using SQL Server as database vendor, which has been changed rarely. Having an upgraded version of SQL Server will not let developer to write a complete new data access layer. Although rare, but if the database vendor get changed to a separate vendor, but

  Posted to Architecture (Forum) by joycsharp on 11/4/2008
  Filed under: architecture, debate, layered architecture, .net 2.0

• Debate: Do We Really Need Three Layer Architecture?

  How many of you changed your database vendor (i.e. Sql Server, Access) after developing an application? How many of your data entities include business logic? I could say, less than 10% in both cases for my case. I found the similar statistics for my other known developers. I guess this is true for less that 10% of the developers around the world. If that’s true, then do we really need to consider Three Layer Architecture (commonly UI, Business Logic and Data Access Layer) as the best practice? Isolating

  Posted to Architecture (Forum) by joycsharp on 11/4/2008
  Filed under: architecture, Asp.Net 2.0, debate, layered architecture

• You can visualize your .NET code with nAML!

  Understanding the architecture and code in software application plays as major factor while building good software products. Along with specification, examples and tools, a new visual modeling technique being introduced, termed as “nAML” (.NET Application Modeling Language), which overcomes the limitation of typical modeling languages in a revolutionary way! Nothing much to say, just download (FREE) it and you can get to know how POWERFUL it is! Here is the project site: http://code.msdn.microsoft

  Posted to Announcements (Forum) by joycsharp on 9/12/2008