Wrox Programmer Forums
|
ASP.NET 2.0 Professional If you are an experienced ASP.NET programmer, this is the forum for your 2.0 questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 25th, 2007, 05:51 AM
Authorized User
 
Join Date: Feb 2007
Posts: 32
Thanks: 0
Thanked 0 Times in 0 Posts
Default Application Architecture

Hello All,
We are going to migrate our asp web project( an ERP project) to asp.net. It is a huge application(containing about 1000 pages). So we have to desing an architecture. But the problem is our team does't have experience in designing nested project. Our project is made up of several nested project as you can imagine an ERP.
for ex.
Main project
   -Sales project
   -Account project
   -MRP project
   -Payroll project

Can anyone suggest us how should we nest our project so that all the modules should be lossely coupled and we can share global resouces of main project such as themes, master pages ect among the nested project. And we can cross reference the assembly among them.
Thanks in Advance.

 
Old July 25th, 2007, 06:14 AM
Authorized User
 
Join Date: Jan 2007
Posts: 93
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to aliirfan84
Default

Brother, I will recomend u following structure(it might not impress u) but I m using in my ERP project:

1) Make shared datalayer(mean datalayer disgin should be general and it should be one for whole project).

2) Make buisnesslayer for each different module and its components. This will be specific to module and its components and will access shared datalayer.

3) Make one master page, put menues on it for whole application & etc. Add other modules projects to here and build them in combined fashion.

I hope it is most simple and commenly used approch in developing multierd big probjects.

Rergards
Ali Irfan

 
Old July 26th, 2007, 10:51 AM
Friend of Wrox
 
Join Date: Feb 2006
Posts: 116
Thanks: 0
Thanked 0 Times in 0 Posts
Default

For objects common amongst the business, the business "rules" are likely also common across the business. Because of that you should consider developing a set of common business objects that would be shared among all modules. For specific differences, each module could subclass a common object as needed and override the specific methods and properties that need different implementations.

That sounds like a huge project and it's a really good thing you are taking the time to consider some design issues first!
 
Old July 26th, 2007, 11:26 AM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Hi there,

You may also want to take a look at this article in the MSDN magazine: http://msdn.microsoft.com/msdnmag/is...ExtremeASPNET/

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Basic Architecture iceman90289 C# 2005 3 March 24th, 2008 10:53 PM
architecture MunishBhatia ASP.NET 2.0 Professional 3 October 6th, 2007 05:24 AM
3 tire architecture rajdotnet ASP.NET 1.x and 2.0 Application Design 1 October 19th, 2006 01:54 PM
Grid Architecture GibiJ SQL Server 2000 3 January 5th, 2006 03:06 AM
Application Architecture ram_siddinen VS.NET 2002/2003 1 January 27th, 2004 12:20 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.