Levon Levonian wrote:
> I thought about it, but I get the pattern constraint error
>
> Error 4 The Directory/@Name attribute's value, '..\..\[DIR]', is
> not a valid long name because it contains illegal characters. Legal
> long names contain no more than 260 characters and must contain at l
koawmfot wrote:
> i am not sure what doc you are reffering to, maybe the help document?
The MSI doc. It doesn't spell it out but between the error and what it
does say, WiX should include empty tables.
> also, would this be two bugs or one if i were to file, and is this a
> bug in the documenta
John Hall wrote:
Yes, all the features are unselected in the feature selection dialog.
I was launching the MSI with 'REINSTALL=ALL REINSTALLMODE=vomus'.
However, on reading the tutorial a bit more closely, those arguments
are for minor upgrades - I removed them and it now has all the
features
JCWrs wrote:
> I've continued to track this problem and I'm still no where. I have combed
> the verbose log, but there is no reference to any removal of the folder I
> install to.
MSI doesn't log when it removes empty folders (as far as I can tell) but
it does log each file deletion. So are th
I am trying to create multiple Wxl files that contain my UIText,
ProgressText, ErrorText and some Strings
However when I build with Light.exe it doensn't create the UIText Table,
ProgressText Table or the ErrorText Table. Am I missing an important step?
candle.exe" -dcodepage=1252 -dlanguage=1033
Hello,
I've been using WiX 3.0.2925 to install some of our COM DLLs (created by
Visual Basic 6.0 SP6).
With WiX 3.0.2925 when I use:
"heat file MyLibrary.dll -out MyLibrary.wxs"
I will often get a mixture of entries (which is what I want) and a
mixture of entries (which seem to be inste
What you see as a detour is something like using ARPNOREMOVE so that ARP
shows only a Change dialog, and then you get into a maintenance dialog
with choices like Remove, Modify and Repair. That'll get you into a UI.
To prevent choosing Uninstall from Right-click on the MSI file you'd
need a type 19
I would assume from part 1 you would have to find some way of determining drive
E versus D/C prior to install or checking to see if it is available. I
struggled with this also and have made it something that the user will need to
input during the installation UI. But if you're trying to look for
Thanks!
1. I've noticed that if I run the setup on a computer that has only a C drive
I have to run it using msiexec with the parameter TARGETDIR=e:\ for both
install and uninstall, otherwise I get an error that says it cannot find e:\.
How can we make a general solution for both computers -
Ah, I see. So, in other words, since MSI/Windows forces the UILevel to 3
when doing an uninstall from Add/Remove Programs, there is no way to
force the installer to show authored dialogs during uninstall. Is that
correct? Or is there a known work-around?
- Brett
> -Original Message-
> Fro
Pass sca.wixlib on the light command line. This file is found in your WiX
install folder. Light will also need to locate scasched.dll and scaexec.dll,
which are in the same folder.
Web site manipulation is not a standard feature of Windows Installer, it is
an additional feature of WiX. As such it
> MSI shouldn't remove directories that aren't empty. Check a verbose log
> to see which files are getting deleted and then when the folder's
> getting deleted.
>
>
I've continued to track this problem and I'm still no where. I have combed
the verbose log, but there is no reference to any
i am not sure what doc you are reffering to, maybe the help document?
anyway, i found another problem, but this one lets the msi actually install
and seems to bury a 2228 error, and is also easy to replicate as well.
what happens now is that i added a progid element above my extension
element, an
Those entries (created by MSI) aren't used for a registered product. You
can remove them and ARP can still remove or modify. Changing them also
makes no difference for the same reason.
What makes different dialogs display according to product state is a UI
sequence condition on the dialogs displa
I'd like to get my bootstrapper exe to be built while I'm building my Wix
file instead of going into the command line and doing it separately. I
figured I could do some kind of ExeCommand to get it to work but I'm not
quite sure where or how to add that in. Can Wix do that? I know I can
execute
You must be using Votive, the Visual Studio plugin for WiX. I don't use
that so, I'm not sure I can help. But, the xml file that you have for
creating the bootstrapper is essentially a Visual Studio project. You
might try adding it to the solution that your WiX project is in, it
might work. Mak
You're confusing me. By "tfs", do you mean Team Foundation Server? If
so, how does it not support MSBuild?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of jcafaro10
> Sent: Monday, July 30, 2007 12:39 PM
> To: wix-users@lists.sourceforg
jcafaro10 wrote:
>
> Figured it out. This works provided there are product .xml files where I
> need them to be. Problem is I'll have to generate this manually b/c this
> is for msbuild not wix and tfs doesn't support msbuild apparently
>
> Edit: Actually I was thinking what if I just had an
I thought about it, but I get the pattern constraint error
Error 4 The Directory/@Name attribute's value, '..\..\[DIR]', is
not a valid long name because it contains illegal characters. Legal
long names contain no more than 260 characters and must contain at least
one non-period character
How do I reference the output of a project as the input to a file?
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using A
Figured it out. This works provided there are product .xml files where I
need them to be. Problem is I'll have to generate this manually b/c this is
for msbuild not wix and tfs doesn't support msbuild apparently
http://schemas.microsoft.com/developer/msbuild/2003";>
Microsoft .NET
I think there is a package for SQL Server Express for the VS 2005
bootstrapper. I am not sure how to specify it in an MSBuild file, but
you may be able to figure that out by creating a dummy setup in VS 2005
and specifying it as a dependency and then looking at the project file.
You can also crea
> I know that to install .NET I need to use a bootstrapper so I made a
> .proj
> file and put this in it, but I need to add other things to the
> bootstrapper
> that won't install from the msi like sql server desktop engine and
> itechlogger but I'm not sure how to do that.
>
SQL Server Express c
I know that to install .NET I need to use a bootstrapper so I made a .proj
file and put this in it, but I need to add other things to the bootstrapper
that won't install from the msi like sql server desktop engine and
itechlogger but I'm not sure how to do that.
http://schemas.microsoft.com/devel
Hi David,
Yes you are correct, if i hadn't be so hasty to start coding the setup i
would have noticed that an example is shipped with wix
[examples\wixui\custom]
a quick check out of the source, and extending mondo seems a pretty simple
task! Works perfectly!
Thanks for the push in the right
In the Registry, installers created with WiX make the entry:
UninstallString = Msiexec.exe /X{}
Which makes the uninstall run with a minimal UI. Is there a way to make
the ARP entry:
UninstallString = Msiexec.exe /I{}
So that it forces the change/remove/repair screen instead?
Thanks,
Brett
-
Mark:
Assuming you have already created your new dialog WXS file. You should be
able to simply edit the WixUI_Mondo.WXS file to insert your new dialog in
the progression.
Or, you could create another WixUI_Mark.WXS file that contains the
definition for a completely new UI in addition to the
You don't want to call one MSI from another. It's not recommended and
the ability to do so has been deprecated. Also, you can't get certified
for Vista if you do that.
Use a bootstrapper to install each of the MSIs sequentially.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Be
> My program comes with a lot of prerequisites but when you uninstall
the
> program I'd like it to uninstall the prerequisites too. How can I get
> it to
> do that? Do I just have to find the uninstallers for the program or
is
> there something else?
You shouldn't do that because prerequisites a
John Hall wrote:
Thanks for your reply. RemoveExistingProducts is
scheduled after InstallInitialize and so has not been run when we get to
the customize screen. It isn't actually migrating any feature states
from the old version either:
It wasn't clear you wer
Hi everyone,
Just so everyone knows, I'm currently using Wix 2, and I'm coding under
Sharp Develop.
Basically is there an easy way to add a extra dialog to Mondo?
I thought a work around would be to build my project using Mondo then use
'dark' to extract the XML, this works fine, however the XML
Hi everyone,
Just so everyone knows, I'm currently using Wix 2, and I'm coding under
Sharp Develop.
Basically is there an easy way to add a extra dialog to Mondo?
I thought a work around would be to build my project using Mondo then use
'dark' to extract the XML, this works fine, however the XML
My program comes with a lot of prerequisites but when you uninstall the
program I'd like it to uninstall the prerequisites too. How can I get it to
do that? Do I just have to find the uninstallers for the program or is
there something else?
--
View this message in context:
http://www.nabble.co
In my installer I'd like it to check if something is already installed on my
machine before trying to install it. There are some prerequisites that the
user needs to have but if they're already installed I don't want them to
install them again. I know it involves checking for something in the
re
Appreciate ya suggestion..It worked without the '#x'..
dunno y is it mentioned to prefix '#x' in the Windows SDK documentation on
registry tables
Stefan Pavlik-2 wrote:
>
>
>
> Stefan Pavlik wrote:
>> Check Registry Value of the MSI file in ORCA editor and you will see
>
> I meant 'Registry
Hi again...
I am not sure that you can directly write to Software\Wow6432Node\ key.
The Wow6432Node key is present only on 64-bit Windows.
I think you should write the value to
Root="HKLM"
Key="Software\APC\APC PowerChute Personal Edition\2.01.100\Shutdown"
If the component is not 64 Bit it wil
Stefan Pavlik wrote:
> Check Registry Value of the MSI file in ORCA editor and you will see
I meant 'Registry Table' not Registry Value.
Stefan
--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com
Panenska 28 | 811 03 Bratislava | Slovak Republic
Main +421
Hi
You should not use the '#x' prefix in the Value attribute.
The light.exe (I think) will create correct value during creation of
the MSI package.
Check Registry Value of the MSI file in ORCA editor and you will see
that the string in the 'Value' column is:
#x#x{4E4F5445530046726F6E7450616765457
Can anyone tell me if the "Value" attribute i have specified is correct?
This piece of code doesn't seems to work when the msi is run..
http://schemas.microsoft.com/wix/2006/wi"; />
Am i using the proper syntax to specify the binary value?
--
View this message in
Hi Folks,
I am new bie to WIX & INSTALL world, We have requirement in our project to
use existing MSI built in installsheild on windows platform that need to be
called using WIX rather intgrated.
1> I need to have some sample codes to invoke the existing msi's built in
Install shei
We have a product which include a number of features. One of these features
installs a virtual website under the Default Web Site. Each feature is defined
within its own fragment
Initially the website element refering to the Default Web Site was added under
the Product element.
We had an issu
41 matches
Mail list logo
