The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Preventing Duplication

I'm puzzling over the best way to design the presentation layer of an eCommerce solution. I'm using a third party component as the API for the eCommerce solution, with presentation and other business rules in .aspx pages. Now, if the eCommerce site is deployed to many different sites on different servers how best would you manage updates to the application, including changes to the .dll and the .aspx pages. Is there a solution to this or is it just a fact of life that there will be some amount of duplication and rolling out updates has to be done manually?
Anon Send private email
Friday, November 25, 2005
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz