Considering the default versioning rules and non-versioned files, I'm wondering
if someone can help me see a better way to handle a problem.
The development team that I support deploys ASP.NET webservices which have
lots logic datadriven by XML files that are installed on the server side.
Unfortunatly this data is not always static. The system will sometimes update
these files with configuration data changes. At the same time, developers
will check in newer versions of these files into future builds. At install
time the developers want to be able to eat their cake and eat it to. They
want to see the changes in the build get staged but they also want to see the
changes the system made persisted. And we aren't talking about a handful of
settings like datalayer connection information, there are literally hundreds of
XML files that could have countless configuration changes.
Short of getting dev to redesign their application ( which was done before I
showed up ), is there anything anyone can thing of that I'm missing that could
solve the problem?
---------------------------------
Never miss a thing. Make Yahoo your homepage.-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
