Re: How to separate an ASP.NET application

My solutions generally consist of multiple projects - a web app with
only the functionality (pages, classes, etc) required to place its logic
on the web, and other projects that might consist of console apps,
winform apps, etc.  And a project of classes that contains statics,
enums, business objects, etc.  The various apps all utilize the project
of classes.

solution
    web app project
    console app project
    winform project
    shared classes project

Claude Petit wrote:
> 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