Hi folks! This might be a noob question, but I haven't been able to find the answer. My scenario is really straight forward:
I have a windows application with several files that lands in a "Program files..." folder. These files are divided into components depending on what kind of functionality there's in them. The files are mostly .net assemblies are not in any way global. They should only be used by my application. I use major upgrade when installing a new version. Now I want to make a release v1.0 of the application and at the same time keep on working with v2.0. The two version which shall run side by side, so course I need to change the UpgradeCode. I also of course make a branch in my source control to manage the v1.0 and v2.0 tracks. My question is: Do I need to make new guids for all the components i v2.0?. In the best of worlds there is no conflict between component in different msi-databases? Best regards // Henrik Carlsson ___________________________________________ Henrik Carlsson | Software Consultant | Sogeti mobile +46 (0) 702 - 20 23 70 henrik.carls...@sogeti.se ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
