Hello,
We are converting an existing Installshield installers into WIX Installer.
Our current installer(installshield) works in this way :
1. There are couple of .sql files which are included in the installers
2. Few variables in the .sql gets replaces with the entries on the dialogs
shown.
Hello,
The attached XML should create the following directory structure, for
our product:
/C:\1Spatial\data
C:\1Spatial\data\dam
C:\1Spatial\data\dam\log
C:\1Spatial\data\lic
/*C:\1Spatial\data\sort
C:\1Spatial\data\obdb
C:\1Spatial\data\obdb\config
C:\1Spatial\data\obdb\default
The attachment does not appear, pasting XML in here:
?xml version=1.0 encoding=UTF-8?
!-- Check/process command line arguments, define default settings.
Command Line arguments are:
goth_product_root Mandatory The directory path containing
the
I have properties set by a DirectorySearch and a RegistrySearch both of
which work as expected with UI but neither of which is set when run in silent
mode:
Property Id=ABCFOLDER
DirectorySearch Id=ABCSearch Path=[SOURCEDIR]ABC Depth=1 /
/Property
Property Id=DOTXYZ
RegistrySearch
Hello,
we need some files (distributed with the MSI) to be in some path only
for the execution of some custom actions. Then, after the installer
finished, the files should be removed.
We've tried simply putting them as File in a component inside a
TempFolder Directory, but at the time of the
Dave says...
Could it be because the things you're looking for only appear in the user's
profile - hkey_users and c:\users ?
When you switch from UI sequence to execute sequence, the intallation engine
switches to the service side and the current user becomes local system and
user-specific
I am actually working on a blog post that describes how to do what you are
looking for now. I have the sample files if you would like them, please
contact me directly and I will email them to you.
John
-Original Message-
From: Manitha Singhvi [mailto:manitha.sing...@gmail.com]
Sent:
OK, I know now I need some virtual pc software for testing installations.
But I still have to clean what I messed up already.
Basically I ended up installing some components to some random, inexistent,
incorrect path (set in a custom action...). I didn't get any error dialog
while installing, but
I don't think it should be anything to do with user's profile: the Directory
search is looking for a sub-folder in the folder containing the MSI
([SOURCEDIR]) and the Registry search is looking in HKEY_CLASSES_ROOT.
InstallScope is perMachine
The problem does occur with MSI 5
-Original
Tobias S Wrote
Use a mapping of the external session object to an internal and do all
the tests against the internal session object. The communication to
the outer world then is limited to a small communication layer which
just passes properties from outer session object to internal session
The log says it's found in a per-user location: Its value is
'C:\Users\kparkes\Documents\ABC\'.
HKCR is just a view merged from HKLM/Software/Classes and
HKCU/Software/Classes.
What does the log say the values of SOURCEDIR and ALLUSERS are in the
property dump(s) at the end ?
-Original
I think the per-user location in the log is a red herring: I just happen to
have the MSI in c:\Users\kparkes\Documents on my test machine.
With or without UI, properties are as follows:
ALLUSERS = 1
SOURCEDIR = C:\Users\kparkes\Documents\
-Original Message-
Re: [WiX-users] Directory and
I don't think Jason is involved in WiX / DTF development anymore. Can
anyone confirm or deny?
I'd do the interface refactoring work if someone from the WiX team said
they would like it done.
From: dbenzhu...@gmx.net
Sent: Tuesday, November 29, 2011
Kevin,
I wouldn't worry about it unless you find a need for it. I was simply
repeating the settings seen from a default WiX CA C++ project.
If you can get the CA to compile, then you can ensure the CA is
properly assigning the property the correct value via inspecting the
log. From there
Seems OK then. Have you tried ICE validation ? Have you compared the UI and
Execute sequences in Orca/InstEd ?
-Original Message-
From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
Sent: 29 November 2011 15:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Directory and
I'm getting several errors for unresolved externals:
Error7error LNK2005: _WcaSetProperty@8 already defined in
installerdll.objwcautil_2010.libInstallerDLL
Error8error LNK2019: unresolved external symbol
_VerQueryValueW@16 referenced in function _FileVersion@12
Orca ICE validation flags up a few warnings (mostly about registry) but nothing
that looks relevant.
InstallExecuteSequence:
FindRelatedProducts (25)
AppSearch (50)
LaunchConditions (100)
...
InstallUISequence
FatalError (-3)
UserExit (-2)
ExitDialog (-1)
FindRelatedProducts
You either link to the pre-existing lib file and simply include the
headers, or you include the headers and source and you don't link to the
lib.
When you installed WiX, it should of setup the WIX environment variable.
Then in your project you should have
It depends how you intend to do that launch. Launching installers from
installers is generally a bad thing. MSI setups can't launch other MSI setups
in any reasonable way; your hosting MSI may fail having installed the driver,
so what about rolling back or dealing with the driver already
I had many on the list request the sample files. As such, I rushed to complete
my blog post.
http://blogs.kungfucoder.com/blog/post/2011/11/29/Database-Installation-using-VCDBCMD-and-WIX.aspx
Feel free to comment, as described in the blog, I do not advertise this as the
ideal way, because of
That does seem overly complex right out of the gate. Have you taken a good look
at the Binary element? This is how I make my files available to my custom
actions without having to copy anything to the local computer. Might not be
what you are after, but it's worth mentioning.
-Original
My main WiX 3.6 source file contains the following lines:
40MajorUpgrade DowngradeErrorMessage=A newer version of
[ProductName] is already installed. Setup will exit. /
...
261InstallExecuteSequence
262 RemoveExistingProducts Before=InstallInitialize /
263 ...
(some
Microsoft used to provide the Windows Clean-up Utility (MSIZAP.EXE was
one common name) but I believe they must have removed it from their web
site.
This might be a viable copy of that same program. They seem to indicate
the author is Microsoft Corp.
Marcus,
A couple general comments, then some specifics.
1) Whenever unexpected things happen, redo the transaction generating a
verbose log. In your case, you need to look at the values for each of your
directories AND look at the log spew related to the CreateFolders action
(both where it is
I'd personally steer away from MSIZap or similar tools (CCleaner does it
as well). I don't think any of these will clean up orphaned Component
registry entries.
If you find the uninstall key in the registry, you should be able to
find the locally cached MSI package. I'd make a backup copy of the
I did in fact managed to find cached MSI files in Windows/Installer folder.
Then I removed entries related to the problematic components with Orca,
saved the MSI and uninstalled without errors.
Is there any place in the registry that I should check as well?
On 29 November 2011 19:19, Hoover,
Is there a walk through anywhere of how you would use those tools to do so?
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, November 29, 2011 1:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] removing
MsiZap was basically a friendly front end for the the MSI CleanUp Utility
msicuu_.exe, or maybe it was the other way round. Either way, the Windows SDK
no longer ships a clean up utility and it's been retired. Any version you find
is going to be old and out of date with respect to later
Not really,
its more just having an understanding how Windows Installer works and
then knowing how to force it to try to cleanup what it can. Though I
should have recommended the cleaner option first, which is to regenerate
the package with the same product/upgrade code but a fixed uninstall.
Finally got the linker errors resolved. I run my msi, and if I leave
the name or email blank, instead of an error, the installer just quits.
Here's the CA:
UINT __stdcall VerifyUserInformation(__in MSIHANDLE hInstall)
{
wchar_t *filePath = LC:\\Log.txt;
log(filePath, LInside
I believe this is the replacement for MSI-Zap
http://support.microsoft.com/mats/program_install_and_uninstall/
Neil
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: 29 November 2011 19:03
To: General discussion for Windows Installer XML toolset.
It seems wcslen doesn't play nice will null pointers. So we should
update those test to be similar to:
if ((userName == NULL)||(wcslen(userName) == 0))
Also, is there a reason you are driving your own custom logging instead
of using WcaLog? Below code redone, verified compliable, that should
I was using the companies custom logs, as I'm not sure where the wcalog
is being saved, or the name of that file. Also, I'm not getting any
kind of error that the user can see or prevent the page from switching
when they fail to put something in the appointed boxes.
33 matches
Mail list logo
