If its an enterprise application consider the scheme given below... And
there is no layer as common...its simply a set of classes with common stuff.
And its not a very good idea to read constants from code files. Put them in
configurations or database.
Layers can go like this...
User Layer -- Pages
Client Side Code (JQuery /JavaScript)
Server Side
Tier 1
Tier 2
Tier 3
-----
-----
Tier N
and you can make as many tiers you want as per acquirement and architecture.
On Mon, Aug 22, 2011 at 12: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
>
--
Best Regards,
Iftikhar Qamar
--
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
