When building a Patch for a setup should a patch file contain all items that
could change or just the ones I know that have changed. For example I have
the following defined:
The two setups I have only differ by one file, say File1. Should
That works only when the corresponding field in the MSI is "Formatted" type. It
may work if you update the in-memory MSI file with the required value prior to
the CreateShortcuts action. I have no experience of doing this, but vaguely
recall people using this technique.
Phil Wilson
-Orig
Hi,
In the Shortcut table of the msi, I want to use a property (ST_NAME) for the
Name column.
The shortcut I am creating is shortcut to an IIS Virtual directory. The setup
could change this location based on user input, so I want the shortcut name to
reflect this change.
I am finding that if I
I created some new dialogs and created a .wxl for my new strings. I
have these dialogs in a WiXLib with the XXX_en-us.wxl included in the
project.
The library project is marked to "Bind files into library". I build the
library without a language specification.
When I use the WiXLib, I specify t
Hi Nick,
> Did you ever get a solution to this? Does anyone have any ideas about this
> problem and how I might go about fixing it?
Sorry, I didn't read the whole of your thread (I didn't realize that there were
other replies).
I've also tried re-jigging my project structure and have got it wo
Which auto-start?
On Mon, Jul 25, 2011 at 6:05 AM, Roy Chastain wrote:
> I think the title says it all.
>
> Thanks
>
> --
> Roy Chastain
>
>
>
> --
> St
Hi Nick,
> I'm trying to create a very simple WiX MSI installer consisting of two files,
however I'm receiving the
> following build error from light.exe:
>
> The system cannot find the file '..\BizTalk Message Archiving Component
> Properties\bin\Deployment
\Modhul.BizTalk.Pipelines.ArchiveMess
I think the title says it all.
Thanks
--
Roy Chastain
--
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual prope
I've found DirectXSetupGetVersion(), so I'll write a custom action to call that.
Rob
On 25/07/2011 11:30, Rob Hamflett wrote:
> I saw in a post from way back in 2007 that WiX provides properties called
> DXMajorVersion and
> DXMinorVersion, but these don't seem to be around anymore (at least, n
I saw in a post from way back in 2007 that WiX provides properties called
DXMajorVersion and
DXMinorVersion, but these don't seem to be around anymore (at least, not in
3.5.2519.0). The
WixDirectXExtension only seems to have properties for getting the pixel shader
and vertex shader
versions
Thank you so much Maksim!!!
That fixed it.
Thanks,
Animesh
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Monday, July 25, 2011 3:41 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] QuietExec in CA
The problem in your code is : Quie
The problem in your code is : QuietExec((LPWSTR)(cmdToEx.c_str()),1000);. You
can't transform char* to LPWSTR this way.
-Maksim
-Original Message-
From: Anand, Animesh [mailto:animesh.an...@igatepatni.com]
Sent: Monday, July 25, 2011 1:58 PM
To: General discussion for Windows Installer X
Thanks a lot Maksim for your help. This really helps.
Thank You,
Animesh Anand
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Monday, July 25, 2011 3:23 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] QuietExec in CA
Instead of Mes
Instead of MessageBox it's better to use WcaLog(LOGMSG_VERBOSE, "Your message").
Here is a working example of using QuiteExec():
LPWSTR pwzCommand = NULL;
LPWSTR pwzSystemFolder = NULL;
hr = WcaInitialize(hInstall, "MyCA");
ExitOnFailure(hr, "failed to initialize");
hr = WcaGetProperty(L"SystemF
Thank You for your reply David.
This is what I am doing.
cmdToEx="\"C:\\WINDOWS\\system32\\calc.exe\"";
MessageBox(NULL,cmdToEx.c_str(),NULL,NULL);(I see the calc.exe path in quotes
in the MessageBox)
hr1=QuietExec((LPWSTR)(cmdToEx.c_str()),1000);
Where cmdToEx is a string object.
I have also
Are you passing "C:\Windows\system32\calc.exe" and not
"C:\\Windows\\system32\\calc.exe".
Just a guess.
-Original Message-
From: Anand, Animesh [mailto:animesh.an...@igatepatni.com]
Sent: 25 July 2011 09:44
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
Thank a lot Maksim. I'll do this.
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Monday, July 25, 2011 2:10 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] QuietExec in CA
Error code 80070002 means "The system cannot find the file s
Error code 80070002 means "The system cannot find the file specified". With
"LOGVERBOSE=1" you will see the command line which QuiteExec runs (this is not
the same as just specifying /v flag for .msi). QuiteExec works fine from a C++
CA.
-Maksim
-Original Message-
From: Anand, Animesh
Hi Maksim,
Thank You for your response.
The verbose logging gave me the error I mentioned in the mail.
I have tried to do this for exe's I know whose paths are valid.Eg:-calc.exe or
notepad.exe under C:\windows\system32 just to see if I can actually get them to
launch.
I pass these with quotes. (
19 matches
Mail list logo
