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. Right now, there's no
solution file for building Votive and I'm struggling to create one that
works properly. A solution file isn't a necessity but it'd sure make it
easier for folks to debug and hack on Votive going forward.
I'm coming to the point where I'm wondering if my work on this is worth all
the trouble. I'm looking for some thoughts from the community on the
following issues:
- Is having a solution file something we should have as a goal?
- Is supporting the standard debug in VS scenario for Votive important?
- 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.
Any advice on how to move forward on this would be appreciate.
Thanks,
Eric
----------
Eric Schultz, Developer Advocate, Outercurve Foundation
http://www.outercurve.org
eschu...@outercurve.org
cell: 920-539-0404
skype: ericschultzwi
@EricOutercurve
------------------------------------------------------------------------------
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
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
