Yan Sklyarenko wrote:
Hello WiX community,
This is a pure MSI question.
I'd like to insert a row into the Directory table, which corresponds to
the root of disk drive, for instance, D:\. But, neither D:\, nor D:
works in DefaultDir column...
Is this at all possible? If so, then how?
Anidil wrote:
Can't we author all the setup components inside an msm?Do we really need wix
then?What all are the advantages of going for wix instead of deploying an
application using merge modules?
By extension, we do not need tools like WiX as we don't need tools like
compilers. We can all
Albert Shamsiyan wrote:
Wix help regarding DigitalCertificate Element, states that the
SourceFile is The path to the certificate file. Is it possible to
extract it from already signed file? If so how? Can I just use a signed
file or I must use the certificate file?
Err, no. Digital
Chris Mumford wrote:
During install I need to start a program that I've just installed, and I
also need to kill it during uninstall/upgrade.
I believe that I can just add a custom action to start it, but what
about to stop it? Is there a non CA solution to this problem?
Wouldn't such a
Christopher Painter wrote:
The WiX `philosophy` seems to be don't add .NET dependencies to your
install and don't redist the framework.Just do an AppSearch/Launch
Condition and tell the user to go do it on their own. Personally
this conflicts with my needs and results in one of the
Chris Eldredge wrote:
I'm trying to create an MSI that installs a .NET assembly and registers
it for use in SQL Server 2005.
The problem is that the SQL I'm executing inside a SqlString is telling
SQL Server to load the assembly, but when I install the MSI it seems
that the assembly
RW wrote:
File Id=MyConfig.XML Name= MyConfig.XML Source=Startup\ MyConfig.XML
/
As it changes and will contain important data, I don't want the uninstaller
to actually remove it.
Generally, this is not the correct way of doing things. The idea is to,
1. install MyConfig.XML with
Karthik Krishnan wrote:
You can set the File's parent Component's Permanent attribute to
yes, which I think accomplishes what you are trying to do.
This generally should only apply to system files.
- Adam
--
Mail Etiquette
==
* Quote properly or not at all. Top posters, this
SaiTeja wrote:
Continuation for the previous mail.
When I start service manually from services.msc, I got error message as
Windows Couldnot start Service on Local Computer - Error 1067: The process
terminated unexpectedly
Try to run it directly from installation location. What error do you
[EMAIL PROTECTED] wrote:
It's a slightly unusual option, but if I was in your shoes I might
consider supplying the application packaged as a wixlib (containing the
main application installation), together with a utility which allows the
reseller to select their template folder. After verifying
Richard wrote:
There are times when I think the unzip files approach is legitimate.
For instance, suppose you have a bunch of data files that represent a
snapshot in time for a dynamically updating service.
Install the initial snapshot as a zip file. The service or custom action
will then
Xin Liu (Intl Vendor) wrote:
In our msi there is a .zip file needed to be unzipped to target folder
during installation. Does Wix directly support this kind of action?
Why? Isn't the MSI file like a zip file?
Anyway, your solution is really nasty. As far as I know, it will prevent
the content
Anidil wrote:
I see that the service.exe has been copied and registered under windows
service console.but it doesn't start automatically.I get the following
message when tried starting manually.Windows could not start the service on
Local Computer. Error 1053: The service did not respond to
SaiTeja wrote:
Condition((NOT VersionNT=500) AND (VersionNT64))/Condition
This is just a side note, but you should almost never use something like
(NOT Version=500). Maybe you are looking for something like
(VersionNT500)? If you do not want to use CDATA section, you probably
can just
SaiTeja wrote:
Hi,
Thanks for Info.
Can you suggest for Msi Logging for XP or 2000
- Property Id=MsiLogFileLocation Value=C:\Install.txt/
- Property Id=MsiLogFileLocationC:\Install.txt/Property
I'm not using this, but my suggestion would be to,
1. DO NOT use C:\ for cruft like log
Adrian Alonso wrote:
Hi! I need to add a launch condition to my product installer to
determine if the OS is Windows XP. My product can be only installed on
WinXP. Do you know which registry entry should I take or if I should use
another kind of launch condition? What I'm looking for is an
Jose Sanchez Saldana (Excell Data Corporation) wrote:
I’m attempting to call sed.exe as an embedded binary from an MSI –
however, it has three dependencies: cygiconv2.dll, cygintl2.dll, and
cygwin1.dll. Does wix have any mechanism, through custom actions, that
would allow sed.exe to be called
robert marshall wrote:
When creating shortcuts for our wix installer we've previously set the
Workingdirectory for the shortcut to be the root directory for the app
in C:/Program Files. Vista complains about users saving stuff there -
which happens when they do a save as and don't change the
SaiTeja wrote:
Hi,
Can any review the wix code for the following and give example for last one
Description=This will install only on Windows XP or later
ConditionNOT VersionNT = 500/Condition
Err, this is NOT VersionNT = 500 which means it will not install only on
one
Richard wrote:
The problem isn't anything to do with Vista, its because your service
has a dependency on something in the GAC and the files don't really
appear in the GAC until after the Commit phase of the install.
Just mark your service as starting automaticly and you shouldn't have
any
Richard wrote:
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
Regarding the service now, I think the problem has a lot to do with the
installation of stuff into the GAC (the recommended way of doing things
after all). All that the service needs is the C runtime
Richard wrote:
In article [EMAIL PROTECTED],
Rob Hamflett [EMAIL PROTECTED] writes:
Publish Event=SpawnWaitDialog Value=WaitForCostingDlg![CDATA[Cos
tingComplete = 1]]/Publish
Do you really need this ![CDATA[]] business?
CDATA sections is not needed in XML. It is only used if
Wilson, Phil wrote:
If you were in fact installing the base VS 2005 merge modules on Vista
instead of the SP1 versions, this might be the Orca issue with dates -
if you open a merge module with Orca it will unconditionally change the
modify date. If you did that to the original VS 2005 merge
Hi,
I have a service I want to install and automatically start with an
installer. Now, the runtime for the service is not available until after
installer completed because the runtime goes into the GAC (it is just
the VS2005 SP1 C runtime).
One solution is to deploy the files locally (as in a
Richard wrote:
In article [EMAIL PROTECTED],
Craig0ss [EMAIL PROTECTED] writes:
Basically my installer installs certain standard letters for use with the
software, if i change the standard letter to incorperate client specific
details and then uninstall the product the modified file is
hina1703 wrote:
Hello Richard,
I am still trying to find out some information as subtle advantages of WIX
over InstallShield looking for a demo project. Do you have any other
example project which you can share with me?
Also are there any power point slides or any info available?
The
Hi all,
I want to install a service, but the service needs a runtime installed
first to be able to run. More importantly, the C runtime.
My current setup is,
Feature Id=ServiceToInstall Level=1 InstallDefault=local
TypicalDefault=Install
MergeRef Id=msvc80 /
ComponentRef
Bob Arnson wrote:
Adam Majer wrote:
How can I structure this such that the merge module is installed
completely prior to installing the component?
That's not how Windows Installer works: Merge modules lose their
identity when merged, so they're just a bunch of components in the .msi
Richard wrote:
In article [EMAIL PROTECTED],
Adam Majer [EMAIL PROTECTED] writes:
How can I structure this such that the merge module is installed
completely prior to installing the component?
In addition to what Bob Arnson said, check your install execute
sequence and look
Rob Mensching wrote:
schema is all documented. The command-lines and the tools to use are
documented.” I’m happy for people to say, “Hey, such-and-such isn’t
documented… can I expect it to remain constant supported and all that
good stuff?” I’ll then go into the tools and see if it is a
Wilson, Phil wrote:
That's correct, Vista uses the same SxS model with Fusion to install the
C++ runtimes as GAC installation, so the runtimes aren't available until
after InstallFinalize.
Solution:
* Install merge module if (VersionNT 600) OR Version9X . In other
words, install the
Jeff Bean wrote:
Adam Majer-2 wrote:
Installing the runtime from VS2005 SP1 using the merge module (yes,
correct version) does NOT work on Vista while it works *perfectly* on
2003 server - both clean installs of the respective OS. Both OSes need
the runtime installed for the program
Peter Marcu wrote:
The wixout is not a pure xml file in WiX 3.0. It has a cab at the
beginning of it that contains embedded binary files.
Wouldn't it be possible to fix this such that it is a proper XML file?
The cab could be embedded in the XML (eg. base64) and the entire thing
would be much
Hi all,
Installing the runtime from VS2005 SP1 using the merge module (yes,
correct version) does NOT work on Vista while it works *perfectly* on
2003 server - both clean installs of the respective OS. Both OSes need
the runtime installed for the program to run.
The install log on Vista
34 matches
Mail list logo
