G
Guest
Hi,
I am building an asp.net 2.0 (vb.net) web app. Whats the best approach so
that it can handle multiple modules being added to it over time. Intitially
it will be a time recording application but over time I will add in a HR
section, invoicing, forecasting and so on.
Should I have 1 project for all of this or should it be multiple different
projects (I mean projects in Visual Studio).
I am thinking of just using 1 project and dynamically showing links to the
modules the user is allowed to see in a masterpage.
This is very high level, any one have any references for books on asp.net
design?
I am building an asp.net 2.0 (vb.net) web app. Whats the best approach so
that it can handle multiple modules being added to it over time. Intitially
it will be a time recording application but over time I will add in a HR
section, invoicing, forecasting and so on.
Should I have 1 project for all of this or should it be multiple different
projects (I mean projects in Visual Studio).
I am thinking of just using 1 project and dynamically showing links to the
modules the user is allowed to see in a masterpage.
This is very high level, any one have any references for books on asp.net
design?