Re: How to separate an ASP.NET application
"Efran Cobisi, cobisi.com" <[email protected]> Fri, 11 Jan 2008 09:34:09 +0100
| Newsgroups | gmane.comp.windows.devel.dotnet.web |
|---|---|
| Organization | cobisi.com |
| Message-ID | <[email protected]> |
Hi Claude, What about coding each package logic into its own assembly? You could then load the types contained in these assemblies using some sort of a plugin architecture [1]; this way you could define the packages (or plugins) you need directly into, for example, your web.config file. HTH [1] http://www.google.com/search?q=.net+plugin+architecture -- Efran Cobisi http://www.cobisi.com 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