.1 and WiX 3.5.2519.0.
I have double checked all the paths and they are all correct. This
machine has no issues building our main products, which are built
using MSBuild 3.5 and 4.0.
Any advice would be appreciated.
Thanks,
Daniel Moody | Deployment Engineer | Gibbs and Associates
Phone: 805-523-0004
E
on my part as I'm not at all fluent in
COM, and I haven't written a raw Windows API program in years. It seems
to me that allowing the UI from my MSI to be used would get me where I
need to be with the least amount of effort on my part.
My 2 cents. Thanks for all your efforts so far
; VMs.
It looks like you can set your EULA but I haven't gotten that far yet.
I hope this helps. Be sure to share any discoveries you make that might be
helpful.
Daniel Moody | QA Engineer | Gibbs and Associates
Phone: 805-523-0004
Email: dani...@gibbscam.com
www.GibbsCAM.com
---
nguage?
I had thought of adding a "dummy" culture to Wix (ie, "de-vg") that would
allow me to have a second German .wxl file with the product name changed
throughout, but I am not sure how to go about this.
Thank you,
Daniel Moody | QA Engineer | Gibbs and Associates
Ph
Path="C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bootstrapper\" />
Everything else is identical to what you have.
Hopefully this might be helpful.
Daniel Moody | QA Engineer | Gibbs and Associates
Phone: 805-523-0004
Email: dani...@gibbscam.com
www.GibbsCAM.com
I intend to avoid at all costs.
Thanks,
Daniel Moody | QA Engineer | Gibbs and Associates
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first
6 matches
Mail list logo