I want to know what is the naming convention you are using for your .msi files. For example I want to organize my setup packages like this:
ProductName-Major.Minor.Build-setup.msi (like "FooBar-1.0.123-setup.msi") and after an update it may become "FooBar-1.1.456-setup.msi" which can be installed alone or on top of the first version. But as far as I can see, there are some issues about changing the name of .msi file. In my opinion, as far as we change our Package ID's, it is safe to change the name of .msi files. So, is it safe to use naming convention I have mention above? Or should I go with same file names like "FooBar-setup.msi" along with my initial and upgrade installer packages? Thanks, Huseyin. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
