Dear All,
I want to create a Wix UI with ListView .
ListView should contain the following: Name, No, pincode
I am using Sharpdevelop tool to create the Listview.
But i am not able to create the Listview with Name, No, pincode.
Any one please help me on this?
Thanks in Advance...
Anil
Hello Gerry,
I have custom actions that handle spaces in path names. Here is an example:
ExeCommand=/install /min_version $(var.min_matlab) /max_version
$(var.max_matlab) quot;[MergeRedirectFolder]quarcquot;
I notice that in your case you quoted the path as [INSTALLDIR]/myprogram.exe.
From: Gerry Reno [mailto:gr...@verizon.net]
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
I don't think that's legal. cmd.exe is not a redistributable file. You
can't include it in your installer.
And if you're building a 32-bit msi on an x64 system, it will definitely
Hello,
I have a custom action that moves some deprecated files from an old
install to a temp directory during a major upgrade and I have another custom
action to move them back that runs only during roll back. I am having trouble
accessing the two properties set by the first custom
On 12/20/2013 09:05 AM, Daniel Madill wrote:
Hello Gerry,
I have custom actions that handle spaces in path names. Here is an example:
ExeCommand=/install /min_version $(var.min_matlab) /max_version
$(var.max_matlab) quot;[MergeRedirectFolder]quarcquot;
I notice that in your case you
On 12/20/2013 10:44 AM, David Connet wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
I don't think that's legal. cmd.exe is not a redistributable file. You
can't include it in your installer.
cmd.exe is not being
On 12/19/13, 5:31 PM, Gerry Reno wrote:
The relevant code section is:
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
CustomAction Id='LaunchSetup' BinaryKey='CMDEXE'
Execute='deferred'
ExeCommand='/k [INSTALLDIR]/myprogram.exe' Return='asyncWait'
On 12/20/13, 9:46 AM, Gerry Reno wrote:
On 12/20/2013 10:44 AM, David Connet wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
I don't think that's legal. cmd.exe is not a redistributable file. You
can't include it
On 12/20/2013 12:47 PM, Edwin Castro wrote:
On 12/19/13, 5:31 PM, Gerry Reno wrote:
The relevant code section is:
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
CustomAction Id='LaunchSetup' BinaryKey='CMDEXE'
Execute='deferred'
ExeCommand='/k
On 12/20/2013 12:49 PM, Edwin Castro wrote:
On 12/20/13, 9:46 AM, Gerry Reno wrote:
On 12/20/2013 10:44 AM, David Connet wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
I don't think that's legal. cmd.exe is not a
On 12/20/13, 9:49 AM, Gerry Reno wrote:
It's not a Windows program. It's a CUI program that you launch from cmd.exe
Which you can still more easily start directly. If you insist in
wrapping the call with cmd.exe then you MUST adhere to cmd.exe's funky
quotation rules.
Do it the easy way and
On 12/20/2013 01:16 PM, Edwin Castro wrote:
On 12/20/13, 9:49 AM, Gerry Reno wrote:
It's not a Windows program. It's a CUI program that you launch from cmd.exe
Which you can still more easily start directly. If you insist in
wrapping the call with cmd.exe then you MUST adhere to cmd.exe's
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 20, 2013 10:03 AM
Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
On 12/20/2013 12:49 PM, Edwin Castro wrote:
On 12/20/13, 9:46 AM, Gerry Reno wrote:
On
On 12/20/13, 10:27 AM, Gerry Reno wrote:
I not certain this will work. It might with something like a .bat file since
the system knows that .bat files are
executed by cmd.exe.
But what is there to tell the system that my exe requires being run by
cmd.exe?
Assuming that your exe is
On 12/20/2013 01:20 PM, David Connet wrote:
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 20, 2013 10:03 AM
Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
On 12/20/2013 12:49 PM, Edwin Castro wrote:
On
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 6:28 PM
On 12/20/2013 01:16 PM, Edwin Castro wrote:
On 12/20/13, 9:49 AM, Gerry Reno wrote:
It's not a Windows program. It's a CUI program that you launch from
cmd.exe
Which you can still more easily start
On 12/20/2013 01:43 PM, Jeremy Farrell wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 6:28 PM
On 12/20/2013 01:16 PM, Edwin Castro wrote:
On 12/20/13, 9:49 AM, Gerry Reno wrote:
It's not a Windows program. It's a CUI program that you launch from
cmd.exe
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 6:46 PM
On 12/20/2013 01:43 PM, Jeremy Farrell wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 6:28 PM
On 12/20/2013 01:16 PM, Edwin Castro wrote:
On 12/20/13, 9:49 AM, Gerry
It seems there is a bit confusion how executables are launched. Here are things
a bit simplified.
Eventually it all comes down to something below ::CreateProcess() that only
launches PE-files (.exe and .coms).::CreateProcess() will fail if you pass it a
.bat file or .doc file or anything else
On 12/20/2013 01:57 PM, Jeremy Farrell wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 6:46 PM
On 12/20/2013 01:43 PM, Jeremy Farrell wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 6:28 PM
On 12/20/2013 01:16 PM, Edwin
On 12/20/2013 02:01 PM, Rob Mensching wrote:
It seems there is a bit confusion how executables are launched. Here are
things a bit simplified.
Eventually it all comes down to something below ::CreateProcess() that only
launches PE-files (.exe and .coms).::CreateProcess() will fail if you
Command line executables with character output launch just fine without
cmd.exe--I do it all the time. The interface is immaterial. Security and/or
execution context (32-bit versus 64-bit) are another matter, but these can be
resolved once you know the true execution requirements.
--
John
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 20, 2013 10:42 AM
Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
On 12/20/2013 01:20 PM, David Connet wrote:
From: Gerry Reno gr...@verizon.net
To:
On 12/20/2013 02:23 PM, David Connet wrote:
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 20, 2013 10:42 AM
Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
On 12/20/2013 01:20 PM, David Connet wrote:
From: Gerry
That's not exactly true. If a command line executable is launched without a
console (such as provided by cmd.exe) it will create one. Unless you did
something magical to prevent that from working...
-Original Message-
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December
2013/12/20 Gerry Reno gr...@verizon.net:
On 12/20/2013 01:20 PM, David Connet wrote:
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 20, 2013 10:03 AM
Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
On 12/20/2013
Aside from all the other good points which folks have made, if there was some
reason to do the following:
'/k [INSTALLDIR]/myprogram.exe'
Is the second double quote above in the wrong place, and should be moved to
the end of the path?
'/k [INSTALLDIR]/myprogram.exe'
--
View this message in
Yes.
For example, (definitely NOT endorsing using cmd.exe to start executables):
C:\cmd.exe /c c:\Program Files (x86)\orca\orca.exe
'c:\Program' is not recognized as an internal or external command,
operable program or batch file.
C:\cmd.exe /c c:\Program Files (x86)\orca\orca.exe
'c:\Program'
On 12/20/2013 03:59 PM, Phill Hogland wrote:
Aside from all the other good points which folks have made, if there was some
reason to do the following:
'/k [INSTALLDIR]/myprogram.exe'
Is the second double quote above in the wrong place, and should be moved to
the end of the path?
'/k
Extra detail was just added to the bug that was also open. The root issue is
that INSTALLDIR is a Directory thus it has a backslash on the end of it that is
escaping the following quote. I've closed the bug by design.
-Original Message-
From: Gerry Reno [mailto:gr...@verizon.net]
Sent:
Your tests need to use a path with a backslash on it. For example:
test.exe c:\foo foo\bar\ c:\baz baz\quuz\
-Original Message-
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: Friday, December 20, 2013 1:46 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Yes, agreed. The illustration was just of one of the many ways that were
tested.
As I stated earlier, I tested both ways including moving the quote to the end.
And the command line produces different results than WIX.
I just got finished another battery of tests without calling cmd.exe and
|ExeCommand='quot;[INSTALLDIR]\quot; quot;[INSTALLDIR]\quot;'
Return='asyncWait'
Adding an extra backslash works.
But as I said, THIS is not intuitive and needs to be documented somewhere.|
On 12/20/2013 04:48 PM, Rob Mensching wrote:
Your tests need to use a path with a backslash on it.
What exactly is not intuitive? The fact that backslash is the escape character
for paths (not sure where that is documented)? The fact that the Windows
Installer ends all folders in backslashes (that is documented in the MSI SDK)?
-Original Message-
From: Gerry Reno
What exactly is not intuitive is whereever you see an example you see
[INSTALLDIR]. You don't see [INSTALLDIR]\ .
If it was so intuitive then why didn't anyone mention it after the first post?
Because it's NOT intuitive. That's why.
On 12/20/2013 05:09 PM, Rob Mensching wrote:
What
[INSTALLDIR] is a dereference of a Property (Directories can act as
Properties after CostFinalize) so that result may not have a backslash (if it
was a Property without a backslash). So, it is easy to forget because it
depends on how it's being used.
Personally, I found the bug report and this
36 matches
Mail list logo
