How to deal with lots of small ASP.NET projects?

  • Thread starter Thread starter Burt
  • Start date Start date
B

Burt

We (IT) frequently have one off requests for one off processes, pages,
etc (load a file into a db, compare data from two tables, place a text
file on a number of shares, etc). What we end up with is a large number
of apps to maintain. Any ideas on grouping or organizing many small
projects like this?

Thanks,

Burt
 
You have to ask yourself if these applications are related in fucntionality
in any way and can therefore be added to another application as an
ehancement, if they are not, can you at least create functionality that
might be common to them all - like a reusable data layer for DB
connectivity, master pags for presentation, common web.config settings
allowing them to be grouped under the same configuration. Any reusablity
across small projects reduces the maintainence burdon - but increases your
testing remit, so there is always a trade off.

Not for everyone, but I give each application a criticality factor - and put
all our similar value/impact apps on similar scaled services or shared
servers. It makes planning for backups etc. easier and allows me to
calculate scaling and capacity on machine level as opposed to an application
level, so it reduces long term planning and capacity management.

I work in avery large company and we get many request for applications that
appear to be required, but if you dig deeper quite often they are not, or
the user can bend their requirements a little to fit an exisitng
applications fucntionality.

--
--
Regards

John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
 
Back
Top