Hello,
I need to copy my own fonts to a folder other than c:\windows\fonts. So I don't
want to install them.
This is because the application I develop (with DynamicPDF) needs to include
this files (DynamicPDF can't handle installed fonts) and I want to reference
to a folder without concerning
Thanks, this clarifies perfectly.
On 10-08-24 5:48 AM, Peter Shirtcliffe wrote:
> http://robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-
> would-you-use-them
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedtype.net]
> Sent: 23 August 2010 16:23
> To: wix
Hello all,
We are trying to connect up XmlFile functions to our installer and had
some interesting problems. Adding a reference to the DLL to the
project and including a namespace in the wxs file - using something
like
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
we expected to b
I think I recall you sometimes have to reboot and/or restart the Msiexec
service
after setting MsiBreak because the Service Control Manager doesn't get the env
update. I haven't used it in a long time so I could be wrong. on the C#/DTF
side I tend to use MessageBox during intitial development
Good ole' MessageBox is the most reliable way to debug C/C++ CAs that I found.
You may be able to set the breakpoint after the MessageBox and then attach to
the running msiexec process.
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Tuesday, August 24, 20
When is my embedded UI called into during the execution sequence? Is it
called during InstallUISequence or InstallExecuteSequence?
On Fri, Aug 20, 2010 at 1:04 PM, Blair wrote:
> Only via your own UI (either embedded, external (requires a bootstrapper
> where you can place your UI), or in your o
Hi,
I am trying to make an installer that has checkboxes to let you add
shortcuts to the desktop and quick launch bar. I was able to get that
working well except for one small part. Right now on the initial install if
you check the box you'll get the shortcut and if you don't you wont. That is
th
Perfect - I had forgotten about your post since I do so few dialogs
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, August 24, 2010 8:00 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Light error with 3.5.2020
On 23-Aug-10 16:57, Wheele
Dear Wix Experts:
We have a CustomAction DLL written in C. How to debug it?
There are a few posts about it:
Post1:
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom-action/
Post2: http://blogs.msdn.com/b/astebner/archive/2005/06/17/430320.aspx
Post3: http://msdn.mi
Hi all,
My installation advertises the installed application's shortcut, so that it
will be
available to all users, and their HKCUs will be initialized.
I now wish to run the just-installed application from the installation (at the
end), but, owing to the above, the EXE is not available till i
Thanks Palbinder.
Good to know it's supported in 5.0.
From: Pally Sandher
To: General discussion for Windows Installer XML toolset.
Sent: Tue, August 24, 2010 2:07:33 AM
Subject: Re: [WiX-users] Wix 2.0: how to change popup wording
1 - not without forcing y
Hi All,
I am having a problem with the HeatProject MSBuild task. I get an error when I
specify an item group that has more than one item as the value for the Project
attribute for the HeatProject MSBuild task. I am using WiX version 3.0.5419.0
and Visual Studio 2008.
Example:
Bob,
Without requiring Installer 4.5 or higher, is there any other way to support it?
Thanks,
Chunlin
-Original Message-
From: Chunlin Liu [mailto:c...@esri.com]
Sent: Saturday, August 21, 2010 10:43 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] M
Hello, Bob. Thanks for reply.
I use WixShellExec for launching file at setup end. My setup package
requires MSI 5.0 and Windows 7 so I want to try MsiLaunchApp.
My code:
Is it possible to use MsiLaunchApp in my case?
-Original Message-
From: Bob Arnson [mailto:b...
Never mind, I found the cause of the problem I am working on. Think
about this verbose thing another time.
Thanks for listening... :)
-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
Sent: Tuesday, August 24, 2010 9:32 AM
To: General discussion for Windows In
OK, well sort of...I had the wrong Configuration and Platform selected.
Now I see "-v" on the candle and light command line. But, not seeing
any more info than not verbose. I guess I am not quite sure what to
expect here.
-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@ophir-spi
On 23-Aug-10 06:11, David Watson wrote:
> I tried using to set this at link time but the @Win64 will
> not accept them unfortunately, just 'yes' or 'no'.
Yes, that's by design. Like I said, the linker doesn't generally change
the data it's linking and the Win64 attribute changes the data in th
On 24-Aug-10 07:26, Alexander Kozlenko wrote:
> Hello. I didn't find an answer so will ask in this mailing list. Anybody can
> explain how can I migrate from WinShellExec custom action to MsiLaunchApp in
> WiX 3.5? Thanks.
It depends on how you use WixShellExec. Note that MsiLaunchApp is
support
On 23-Aug-10 16:57, Wheeler, Blaine (DSHS/DCS) wrote:
> C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ResumeDlg.wxs(18
> ) : error LGHT0197 : The Windows Installer XML variable
> !(wix.WixUICostingPopupOptOut) is unknown. Please ensure the variable
> is declared on the command line for
For some unknown reason I am getting the wrong assembly into my MSI when
the solution is built on my Team Foundation Server (TFS) build agent.
To resolve this problem I would like to get a complete list of the files
that are going into the MSI. I tried adding "-v" to the Compiler and
Linker Tool S
Hello. I didn't find an answer so will ask in this mailing list. Anybody can
explain how can I migrate from WinShellExec custom action to MsiLaunchApp in
WiX 3.5? Thanks.
Alexander Kozlenko
--
Sell apps to millions thr
http://robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-
would-you-use-them
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: 23 August 2010 16:23
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Shared files/registry question
Thanks
I don't think you understood me. I think your only option is to make
your MSP's uninstallable in this case as there's no other behaviour that
will allow your MSP's to be uninstallable but not affect the shared
files.
This effectively means users can't downgrade once they've upgraded using
the MSP
1 - not without forcing your package to be Windows Installer 5.0 only.
Windows Installer 5.0 is only available on Windows 7, there's no
redistributables for any earlier versions of Windows. If you're happy
with that, knock yourself out.
2 - see above.
Palbinder Sandher
Software Deployment & IT Ad
24 matches
Mail list logo