It was my understanding that putting full path into Name wouldn't work. Everything I found online said what I did is the way to do it.
I had a similar thought about an hour ago while driving about c_drive not getting redefined properly for the uninstall and will try to validate if that's the problem later this afternoon. I do see it and all the directories getting property changed to the right path prior to the FileRemove entries in the uninstall log, though. On Oct 10, 2013 12:47 PM, "Nicolás Alvarez" <nicolas.alva...@gmail.com> wrote: > Your CA_SetCDrive is not being run during uninstallation. You'll > notice the uninstall log refers to C:\CDrive\ all over the place. > > I don't understand why you need that custom action at all. Can't you > hardcode C:\ into the Name attribute? > > -- > Nicolás > > 2013/10/10 Walter Dexter <wfdex...@gmail.com>: > > I posted this at Stackoverflow as well, but I'm just at a loss for what > to > > even look at, so I'm hoping someone can point me in a good direction. > > > > I have been using WiX to create an installer for my project. It's fairly > > simple, just drop some files in three different directories and run a > > VBScript to generate one last file. > > > > I'm a total WiX and MSI noob. The "standard" thing to use at work is > WISE > > but I just can't figure out what to do with that at all, so I gave WiX a > > try. > > > > After some difficulties with the VBS I got the install working. When I > > uninstall the package disappears out of Control Panel but the files that > > were installed are still there. I know the one I generated on the fly is > > going to be unless I do something special to remove it, but the others > > should just go away, right? > > > > I have install and uninstall logs, and also have posted the WiX source > > file. Links are below. > > > > Any help is much appreciated! > > > > install log< > https://docs.google.com/file/d/0B0qy0SfToYUzMUJYMk00UjhreDg/edit?usp=sharing > > > > ( > > > https://docs.google.com/file/d/0B0qy0SfToYUzUUtXVUxpQ0lESm8/edit?usp=sharing > > ) > > > > WiX source< > https://docs.google.com/file/d/0B0qy0SfToYUzR0FDMXc2cXhvMDQ/edit?usp=sharing > > > > ( > > > https://docs.google.com/file/d/0B0qy0SfToYUzR0FDMXc2cXhvMDQ/edit?usp=sharing > > ) > > > > uninstall log< > https://docs.google.com/file/d/0B0qy0SfToYUzUUtXVUxpQ0lESm8/edit?usp=sharing > > > > ( > > > https://docs.google.com/file/d/0B0qy0SfToYUzMUJYMk00UjhreDg/edit?usp=sharing > > ) > > > > Note that this is being installed on Server 2003. > > > > The package is using explicit paths and drive letters. I know that isn't > > considered best practice, but that's where the files need to go. This > > doesn't go to a variety of computer types and configurations; there are > > over ten thousand of these systems in our retail locations and they're > all > > identical. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
