Can someone explain what "xcopy deployment" is, or point me to examples/references? Or point out alternative installer mechanisms that might meet my needs?
Background: I need to distribute a C# .NET application family. It is a series of data analysis softwares, with preloaded data (eg, Texas birth data). Each customized version has different data files, different auxillary files, etc. There are many customized versions. The application was previously in C using curses. Distribution was pretty simple. For each customized version (there could be several on a CD), I put a zip file, a batch file, and the unzip executable in it own directory on a cd. To install, the batch file unzipped everything into several hard-coded directories, copied some icons to the desktop, and displayed some messages. The old installation mechanism looked "clunky", but worked great. I'd rather not keep track of versions. If a user installs a new version, I'd like to simply overwrite any existing files. There is no need for them to keep the "old version". I'd like to avoid the complexity of having to deal with hundreds of different version numbers and GUIDs. I'm concerned that some mistake may make it fail to upgrade. I've read through the wix tutorial. I'm trying to reduce the great complexity I'm sensing from windows installer, figure out a simple, attractive install mechanism. Daniel Goldman http://www.ehdp.com/vitalnet/ 425-235-4747 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
