Thanks. I just got to the point in trying the OFFICAL_WIX_BUILD debug build approach, where it correctly informed me that I don't have all versions of VS installed. And since I have had enough issues with VS2013 and VS2010 behaving, and we are in a critical phase of release, I won't be going down this path any further for now.
The bundle/package which I am trying to debug the wix ca is very stable <smile/>, if I do say so myself, and only a few days away from a release deadline. So taking that approach and swallowing my 'don't run tests on the dev machine' self imposed rule, seems to be a better alternative. And yes I need to get these network access issues figured out so I can do remote debugging. The dev is in a domain and needs to be to access build resources. The VM server and VMs are not in that domain and VS wanted both systems using a common context. (But I need to dig deeper into remote debugging.) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Debug-delopment-story-tp7597968p7597974.html Sent from the wix-devs mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
