I don't see how #2 is distinct from #3. I also don't see why #5 is required. It would be better to replace it with a configuration layer (as Iftikhar suggested in this thread)
On Aug 22, 9:08 pm, "P.Bixam" <[email protected]> wrote: > Hi All, > > I need any advice regarding n-tier architecture... > As of now I am following the bellow structure, > > 1. UI-Layer - aspx, aspx.cs, Javascript, Styles > 2. Business Layer - Invoking DAL Objects, Caching, Auditing (Any Adivce > here) > 3. Business Entity - Classes with Properties > 4. Data Access Layer - Database interactions > 5. Common Layer - Constants, Singleton class > > Can we have any more layers for any other purpose...... > or > Can we elaborate the existing layers.. > Thanks & Regards > P. Bixam -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" 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/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
