We are using FireDaemon for hosting services, instead of writing our own
services.
When using the OEM versioin, we need to do all the install ourself, and that
we want to automate during the installation of rest of the software, but it
seems like we cannot use the normal way using ServiceInstall an
I thought Windows supports more than 260 characters by now?
According to this:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath
We run into path problems way to often with this..
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
Ok, the clue is to make sure you have 4 digits for the Bundle, when one
installs an new version of the bundle, it uninstalls the previous bundle
after installing the new one.
The difference is that one get two logfiles when installing the new bundle
when things are correct, the last one with action
Ensuring that it's there should not be the same as you install it :)
Anyway, I need to detect if this feature is installed, so i can abort the
install if it's missing, It's easy to detect IIS and .net, but is there any
examples on how to do this feature checking?
Is WMI really the way to do it?, w
Does it use 3 or 4 digits?, ie, 1.0.0 or 1.0.0.0 ?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-entries-in-ARP-tp7579932p7596769.html
Sent from the wix-users mailing list archive at Nabble.com.
-
I'm creating lots of small msi's so I can modularize my installation package,
and have been using the bundle feature (Burn?), to make an Exe that can
install everything.
The problem with this is the UI.. I have somewhat managed to make UI in the
MSI, but I cannot use that UI, and need to make an U
If I want to build the src\Setup, to see what is connected where (there are
some files i cannot find etc, which probably are created during build), How
do I do that?
This tells me to use msbuild:
http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html
but the rebuildAll.cmd in src\
aha, you said it did not work with < so..
check this?
http://robmensching.com/blog/posts/2008/11/3/how-to-determine-if-you-are-installing-on-windows-client/
VersionNT64 should be 601 for both server2008r2 and windows 7x64 (but not
set(undefined) on Windows 7, 32bit)
--
View this message in c
the wxs file is an xml file, is yours valid xml?
why not use CDATA on the second condition also?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Show-Hide-a-Text-Control-on-Server-Installation-tp7595834p7595835.html
Sent from the wix-users
commandline or msbuild?
On commandline you can add -gg to generate guid's when heat is run, or -ag
to use "*" instead.
With the msbuild task I use this: GenerateGuidsNow="true" to generate them.
I use msbuild, and have heat setup like this:
which gives me a file like this:
http://schemas.micr
That is not valid XML, wrap it into an CDATA block like this
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/block_install_on_os.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Build-issue-tp7595557p75
anyone?, or is it perfectly ok to store this in hkcu for perMachine installs?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-registrering-shortcuts-when-using-perMachine-installations-tp7595220p7595335.html
Sent from the wix-users ma
How would that commandline be for that case?
If you have wxl files for both languages I kinda understand it, but here I
was including the IisExtension, and using nb-NO cultures which it did not
contain, If I then had to get the english wxl to make it to fallback to
that, I'm kinda just as far.
But
yes, it doesn't need to be an tree..
The main msi have just main node+node if one want to exclude installation of
shortcut on the desktop.
the other three msi's only have one feature, so the selection in the bundle
would only be to select if one want to install all services and the client,
or onl
It seems that with an Bundle, one cannot have feature selections?
So that one cannot choose to install some of the included packages?, that
limits the usage somehow..
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Main-MSI-with-sub-msi-s-tp759522
scubasteve2 wrote
> A bundle can contain a collection of executables, MSIs, MSPs. They can
> all be compressed within the bundle. Read up on Burn and WixStdBA and
> WixManagedBootstrapper.
Ok, but an bundle itself will be an Exe-file right?, not an MSI?
Will read more about this, I was not sure
I found an small issue when I was building msi for IIS application, when you
include WixIIsExtension, and you set your culture to say, "nb-NO", then I
was getting lots of errors like this:
error LGHT0102: The localization variable !(loc.ConfigureIIs) is unknown.
Please ensure the variable is defi
I'm creating four MSI's now, three MSI's are setting up each an WebService,
and, one main MSI that installs an clientapplication.
Today, these are separate MSI's, and will probably be that for those who
want to install separately.
But, the main MSI, we want to be made so it includes the other MSI'
This example:
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/create_start_menu_shortcut.html
If one takes that example, and changes it a little, Allusers=1 and HKLM in
registrykey for the shortcut component
http://schemas.microsoft.com/wix/2006/wi";>
*
Was there any solution to this?, I have the same problem, ICE57 when I
install with ALLUSERS=1
The RegistryValue for the shortcut's keypath is registered only on HKCU, if
I use HKLM og HKMU I get the ICE57 error.
Someone up in the thread said you should ignore it, but it's an error so it
dont produ
20 matches
Mail list logo
