Hi Blair !
thx for your answer, i tried they same .msi file on my laptop and the text
didnt disappear... but it is the same OS WIN XP Professional but not the
same Service Pack oO
i cant believe this will make something
The error when building from the commandline means you must add "-ext
WixIIs
I think you need a & or ! before the Feature Id. Take a look at the
"Condition Statement Syntax" topic in the MSI SDK.
On Thu, Nov 5, 2009 at 5:05 AM, SD_GOTH wrote:
>
> Hello,
> I have an installation package with 2 features. At end of installation I
> want to display a checkbox for further act
Most likely caused by the duplicate FileSearch elements. There are a couple
scenarios with AppSearch that just aren't handled correctly. The AppSearch
design is a real pain and it always takes me a while to finally sort out how
to make it all work.
On Thu, Nov 5, 2009 at 9:52 AM, Richard wrote:
That sounds like the correct part of the File Versioning rules. Read the
blog entry and really the "correct" way to update files installed by the
Windows Installer is to use the Windows Installer to update them. However,
since you are dealing with unversioned files your work around will probably
be
Personally, I'd just do the Major Upgrade with a clean install and call it
good. The WiX toolset has 159 files and we do Major Upgrades all the time.
It is easiest way to move from build to build. If the performance seems
reasonable for your application, I'd recommend it.
On Sun, Nov 8, 2009 at 1
On Sun, Nov 8, 2009 at 10:39 PM, John Robbins wrote:
> Hello K,
>
> Glad my blog entry could help. However, I didn't go into the icon stuff as I
> figured that was common knowledge, but that was a mistake on my part, I'm
> sorry! You've done everything right so far. :)
Not common knowledge but
Hello K,
Glad my blog entry could help. However, I didn't go into the icon stuff as I
figured that was common knowledge, but that was a mistake on my part, I'm
sorry! You've done everything right so far. :)
The icon for SETUP.EXE is defined in the in a .RC (resource compiler) file.
What I copy
On Sun, Nov 8, 2009 at 1:05 PM, John Robbins wrote:
> K,
>
> Here's how I got SetupBld.exe from WiX to behave like you wanted:
> http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.
Oh, I think I've got it now, or at least am getting there
hi All,
Problem:
I have installed some files, registry keys, directories and shortcuts from
my CoffeeShop.msi, this was developed using Wise for Windows Installer.
Then i found WIX, and developed and new product and a new MSI. The new msi
is called CoffeeCo.msi.
Now, when i execute my CoffeeC
On Sun, Nov 8, 2009 at 1:05 PM, John Robbins wrote:
> K,
>
> Here's how I got SetupBld.exe from WiX to behave like you wanted:
> http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.
John, thanks for your response and well-written blog entr
According to my understanding, I've tried to summarize all information and
the solution in our blog:
http://blog.syntevo.net/2009/11/08/125770902.html
If something is wrong, please let me know. Thanks in advance.
Tom
Thomas Singer wrote:
> Thanks for the hint to the File Versioning Rules:
K,
Here's how I got SetupBld.exe from WiX to behave like you wanted:
http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.
Hope it helps!
John
Wintellect
http://www.wintellect.com
877-968-5528
>-Original Message-
>From: kerbe...@n
Blair,
Thanks for the explanation. Regarding your last paragraph about matching up
GUIDs between installs.
"The only way that happens is by making the component guids match. And the
best way to do that is to not autogenerate them, or if you must autogenerate
them, use "*" as the component guid v
Hello,
I am running the most current stable build of Wix 3.0. I'm delighted
with the product on the whole but I've reached a sticking point in
distributing packages of my product.
Basically, I preferred to have "fancy" electronic packaging for my
product and as such preferred not to use the defa
Thanks for the hint to the File Versioning Rules:
http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx
Do I understand it correctly, that file versions and languages solely apply
to .exe/.dll or similar files, but not to, for example, .jar files which are
nothing else than .zip files? Th
15 matches
Mail list logo
