Project in modules

[Marre]

Hi all!

I´m using c# and asp.net to do an application.
I want to do this application in modules. A customer should be able to buy
the modules he/she are intrested of.

What are the right way to here? Should I create the different modules in
different projects, or should I just hide the modules not bought? Or should
I do something else

Any thoughts or links are very welcome!

Regards
Marre

 

[hashimisayed]

With a web application, you probably want to deploy the application as
a whole and then based on the user's login, determine what type of a
license they have. For example, lets say you have three modules (A, B,
and C). You could expose the functionality of these modules via
drop-down menus. Furthermore, lets say you decide to create three types
of licenses: Standard, Professional, and Enterprise. When a customer
purchases a license, you have to make an entry for him in the database
and store the type of license he has purchased. When he logs in, enable
and disable certains menu items based on his credentials.

With web applications you have a central deployment server, so there is
no client footprint for you to deploy a subset of the application
(i.e., you can't deploy module A to customer One and then modules A and
B to customer Two). Therefore, you have to deploy the whole application
and then use some criteria to determine how to expose a piece of
functionality to the user.

Having said that, I would recommend that you have a look at smart
clients, if you are not familiar with them already. Smart clients
provide the benefits of a web application and a windows desktop
application. Have a look at the following and I can elaborate further
if this is an option.

http://msdn.microsoft.com/smartclient/understanding/definition/default.aspx


sayed

 

[Marre]

Hi Sayed!

Thanks for youre answer. That was exactly what I needed

Regards
Marre