The issue is that we use the App Path\Path registry value to specify additional paths for our application. We use the full name of the application which is longer than 8.3. But because the verb registration uses the short path name, the App Path entry is not found when the application is launched by clicking on a document for our application, and so the dependent dlls are not found.
I could add an App Path\Path entry based on the short name, except I don't think I can reliably deduce the short name to register. Most likely it will be BLAH~1.EXE, but can I guarantee that? > -----Original Message----- > From: Bob Arnson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 22, 2006 4:43 PM > To: Mike Dimmick > Cc: Arnette, Bill; wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] <Verb> question > > Mike Dimmick wrote: > > It may well have problems if you use a long path with > > spaces in it. This might be considered a bug (I'm not sure > if Windows > > Installer would properly quote a [#TargetFileId] expansion). > > It doesn't add quotes, whether they're needed or not. Hence the short > path recommendation. > > -- > sig://boB > http://bobs.org > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
