1. Have the user copy it to a location. Put said location somewhere
in the Uninstall UI. There is no CopyFiles Action during uninstall
2.In your installer, write a conditioncheck etc that checks for the
location you gave in 1.
3. Check for File in Location.
4. If file exist, replace default c
Yes, the easiest way to Fix that:
1. Copy original UI File from WixSources into your Dev Sources.
2. Rename Your Copy, as in WixUI_IntallDir-
3. Change the UI Reference you noted below to point to the file from step 2.
Quoting Kelli Hendrickson :
>
> Thank you. I did take your advice and look a
Use Programs and Features to Uninstall Wix, then move your project out
of your Dev directory. Second, Delete your Dev Directory, then
redownload Wix37.exe and Wix37-sources.zip. Unzip the sources back
into your Dev Directory. After this open your Gui source Files in
your project, and Ren
Put in Each Cab you took out then comment out all the Cabss in the
media list, one at at a time. If the first one suceeds, add the
second until you get down to the nth one where 1 < n < 31. The one
you uncomment last will be the one that can't be built, assuming you
start at the top. Tha
The Config.msi Folder is a Hidden System Folder that is created by
Windows. Only SYSTEM, and the Administrators Group should Be in the
Security Tab list, each having Full Access. If the Admin Remoting in
is not a member of the Administrators Group, you may have issues. By
Default a local
See here:
http://connect.microsoft.com/VisualStudio/feedback/details/731094/ghost-msbuild-exe-in-vs11-when-using-custom-task
Sounds like you may need a Service Pack
Quoting Tony :
> I guess I could disable those three ICE validators as they always seem to
> be the ones that blow-up with the "I
ICE38:
http://stackoverflow.com/questions/12860316/ice38-component-installs-to-user-profile-error-for-a-specific-component
ICE64:
http://stackoverflow.com/questions/4627861/wix-the-directory-is-in-the-user-profile-but-is-not-listed-in-the-removefile-tab
ICE91:
http://stackoverflow.com/quest
Does this link help?
http://blogs.msdn.com/b/astebner/archive/2011/05/16/10165211.aspx
Quoting Steven Ogilvie :
> Open up the MSI in ORCA and goto InstallExecuteSequence element.
> Sort the sequences in numeric order and see where your custom action
> is being called now, perhaps it has been
Download the Original Installer, attempt to repair the install, finish
the repair, and do a clean uninstall. Otherwise, download your new
installer, and this tool:
http://www.piriform.com/ccleaner
Use Tools > Uninstaller > Remove from Registry.
Out of curiosity, which step is failing? You
I have a huncgh that the installer WiX Uses now is a burn style
installer, because the install requires a check for the .NET 4
Framework.
Quoting Jens Teutenberg :
> I don’t like the installer which is used since V3.6 (Wix36.exe, Wix37.exe).
> Why it isn’t possible to release a MSI file as us
See my post that is Split from this one from this one. That product
doesn't exist due to the syntax error.
Quoting wix-users-requ...@lists.sourceforge.net:
> Send WiX-users mailing list submissions to
> wix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide W
Not to Butt in, but below may be a syntax error that is contributing
to your issue.
Problem: The Double Slash between the Pre-processor variable and the
file are not needed, even escaped
Solution:
Reason: The Pre-processor variable when expanded includes the trailing
backslash
Rewri
12 matches
Mail list logo
