On 07-May-14 12:14, Eric Schultz wrote: > So, I've been working on a cleanup of the Votive to try to mesh it > with the Python Tools for Visual Studio as much as possible.
I'll donate an entire month's WiX salary plus bonus to the cause! > - Is having a solution file something we should have as a goal? Yes, with priority in line with how much it helps you. Is the SharedProject stuff causing the problem? > - Is supporting the standard debug in VS scenario for Votive important? The whole debug-a-package scenario is pretty non-standard... > - Should Votive be installed at the system level, thereby requiring a > developer to uninstall the official version of Votive (but not the Wix > dlls somehow because we need those) in order to debug, or should we > figure out a way for Votive to install at the user level? This would > probably require the relevant the parts of the Wix API used in Votive > be installed at the user level with Votive. When Votive started, VSIXs weren't an option. It would probably work fine as a VSIX though some things like templates assume a per-machine install of WiX (toolset and MSBuild). The old-school "experimental hive" was the solution for having a package in your normal instance of VS and developing it in the Exp instance. Maybe these days it's having multiple versions of VS side-by-side... I'm all for making whatever changes make it easier to develop Votive, but not if it makes you crazy first. :) -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
