Re: How to separate an ASP.NET application

Now there's a big question.  Read up on N-Tier architecture
to start out.  You will have to develop a core product and then
open the ability to add other components.  When it comes to
business applications, every business likes to do things a little
different and therefore this is where you have to be the most
flexible.

Here are some more things to think about:

1. Is everyone using the same database?
2. Is everyone using the same code base when running the app?
3. If there are different code bases, how do you handle core product updates?

Good Luck,

Robert Taylor
Sr. Web/Systems Developer
Robert Half Technology

--------------------------------------------------
From: "Claude Petit" <[email protected]>
Sent: Thursday, January 10, 2008 10:07 PM
To: <[email protected]>
Subject: [DOTNET-WEB] How to separate an ASP.NET application

> Hi, I want to know how I can divide code for different client setup. The
> problem is I have a big application and I need to make packages to respond
> to client neeeds. By exemple, a client might just need something (some
> functionalities in an ASP.NET page), and it doesn't require something else
> (some other functionalities in an ASP.NET page). This way, I could invoice
> them for only what they need. I just want a way on how to make that. Tanks.
>
> Claude Petit
>
> ===================================
> This list is hosted by DevelopMentor®  http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com
>

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com