[WiX-users] Practical use of wixlibs

I can't find any documentation on best-practices when creating either merge modules or wixlibs, only procedure documentation on how to create them. Let's say I create a wixlib (or msm) with multiple components that make up a large C++ library. Someone making an application with that library can th

[WiX-users] [SPAM] Re: Shortcut creation seems to cause sxs assembly error in Event Viewer

Open the app.exe in a text editor and search for the 'manifest' (or use a manifest viewing tool), generally close to the end of the PE file. The embedded manifest should declare any SxS dependencies. When the windows loader cannot find one of the SxS assemblies declared in the embedded manifest i

Re: [WiX-users] Shortcut creation seems to cause sxs assembly error in Event Viewer

Start Here: Visual studio redistributable & side-by-side / DependentAssembly error - The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown -- View this me

Re: [WiX-users] How to handle a context menu component on install/upgrade?

2013/9/30 victorwhiskey : > Hi, > > I'm trying to install/upgrade a component that is a context menu handler. > I'm trying to see how others do this, especially on upgrade. When upgrading > the component is installed and explorer is using it. Is it possible to do a > upgrade without restarting expl

[WiX-users] How to handle a context menu component on install/upgrade?

Hi, I'm trying to install/upgrade a component that is a context menu handler. I'm trying to see how others do this, especially on upgrade. When upgrading the component is installed and explorer is using it. Is it possible to do a upgrade without restarting explorer and without rebooting the machin

Re: [WiX-users] WiX Disaster -- How did I cause it??

Not a problem, The Windows Error Console confirmed my hunch. I now wish I could join my original message with the long stream so this makes sense in the future. In effect, you were having the installer look 3 levels deep into 2 non existent directories 1. The \ from the Pre-processor. 2. The \\ c

Re: [WiX-users] WiX Disaster -- How did I cause it??

2013/9/30 : > See my post that is Split from this one from this one. Don't use mailing list digests. It makes it almost impossible to reply properly to messages. -- Nicolás -- October Webinars: Code for Performance Fre

Re: [WiX-users] WiX disaster -- how did I cause it?

2013/9/30 Charles Jenkins : > As always, thank you all for trying to help. > > Rob, I took your and Phil's advice and scoped out the Event Log. Indeed it > appears the missing component is that user-specific registry key that I > personally don't want anyway, but MSI seems to require: > > Detecti

Re: [WiX-users] WiX Disaster -- How did I cause it??

ecyoung, Thanks. I fixed the syntax error you pointed out, but I forgot to say so in my earlier letter. I haven't dared try the installer on Terminal Services, but it does work locally without those backslashes. I appreciate your help :-) -- Charles On Monday, September 30, 2013 at 2:24 PM,

Re: [WiX-users] WiX Disaster -- How did I cause it??

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

Re: [WiX-users] WiX disaster -- how did I cause it?

If each user gets the repair just once because of that that user registry item, well that's normal. You defined a registry item for "current user" so Windows will create it each time it sees a new user, and on Terminal Server that can be a lot. If that's the case, it's normal, and the serious issue

Re: [WiX-users] WiX disaster -- how did I cause it?

As always, thank you all for trying to help. Rob, I took your and Phil's advice and scoped out the Event Log. Indeed it appears the missing component is that user-specific registry key that I personally don't want anyway, but MSI seems to require: Detection of product '{EC784F33-0A7C-4899-875B-

Re: [WiX-users] WiX disaster -- how did I cause it?

Also, do you have Dev, QA and Prod instances of this terminal server? It's always a good idea to test your designs in a lower life cycle before promoting into production. Regards, Chris From: "Phil Wilson" Sent: Monday, September 30, 2013 9:37 AM To:

Re: [WiX-users] WiX Disaster -- How did I cause it??

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

Re: [WiX-users] WiX disaster -- how did I cause it?

There'll be an entry in the Windows event log, an MsiInstaller entry, that should say something about what component was missing and needed restoring. If your install removes by design anything that your MSI installed, then you'll need to do something about that. If the original install required a

[WiX-users] How to replace action on next button

Hi there, I am using mondoUI, and I customized CustomizeDlg. Now I want my customized dialog to show right after Welcome Dialog. So I did it like in tutorial: 1 1 1 1 Problem is that it is not working. When I click on next button at WelcomeDlg, the window with License Agreement shows

Re: [WiX-users] WiX disaster -- how did I cause it?

Oops. Pardon the noise. I see I can't just set Advertise="no". I'm going to have to work more to understand Keith's example. -- Charles On Monday, September 30, 2013 at 9:57 AM, Charles Jenkins wrote: > Keith and Rob, > > Thanks for the replies! Pardon me if I'm being thick, but does all th

Re: [WiX-users] WiX disaster -- how did I cause it?

Maybe but, personally, I'd try to understand the root cause of the issue. On Mon, Sep 30, 2013 at 6:57 AM, Charles Jenkins wrote: > Keith and Rob, > > Thanks for the replies! Pardon me if I'm being thick, but does all this > mean that if I set Advertise="no" on the icon, the problem would just

Re: [WiX-users] WiX disaster -- how did I cause it?

Keith and Rob, Thanks for the replies! Pardon me if I'm being thick, but does all this mean that if I set Advertise="no" on the icon, the problem would just go away? -- Charles On Monday, September 30, 2013 at 9:31 AM, keith.doug...@statcan.gc.ca wrote: > I've made use of the below for a w

Re: [WiX-users] WiX disaster -- how did I cause it?

I've made use of the below for a while which uses an unadvertised shortcut: Note that we have a front end we've built to automate some of our WXS generation process (that's why the Ids look funny). This is actually from the front end

Re: [WiX-users] WiX disaster -- how did I cause it?

To diagnose, you'll want a log file, see bullet #2 here: https://firegiant.zendesk.com/entries/24024218-Create-a-log-file- The feature your using is the Windows Install resiliency/install-on-demand feature because your shortcut is advertised. That's normal, you can read about it in the MSI SDK. Th

[WiX-users] WiX disaster -- how did I cause it?

Hi! I'm a WiX noob, trying to write a simple installer for an in-house product. My installer caused a computing disaster, so obviously I've done something wrong, but I don't know what. The disaster is this -- and believe me, I know at first blush it sounds nuts: If I put the installer in a publ