Could you explain what you mean by updating the files version? Is this a .NET
COM assembly? If so you can use the binding references to set the version in
the wix code so that it automatically sets the version number in wix to match
the assembly.
Neil
Neil Sleightholm
X2 Systems Limited
I've got a customer reporting installation failures. In fact, msiexec.exe is
crashing. The log
indicates that this is happening during RemoveExistingProducts:
MSI (s) (4C:98) [16:40:21:030]: Doing action: RemoveExistingProducts
Action 16:40:21: RemoveExistingProducts. Removing applications
I currently work (as you all probably know by now) on an installer for our
software.
Now I have a new problem which I need a bit of input on.
My installer installs five windows services. This is all good and the services
are installed correctly.
They are not started for various reasons, but
This isn't quite as magical as it sounds. I think your problem is that you
think that you're REbuilding the extension, while it does some kind of
incremental build. I've seen this happen a lot, but was never able to track the
root cause.
PS: you have a lot more source code in
Are you getting the error early in the process, like around FileCosting?
Check a verbose log.
Ran into this a little bit ago and added the following property
Property Id=MSIRESTARTMANAGERCONTROL Value=Disable /
This resolved the issue for me.
--
View this message in context:
There is defiantly a Domain attribute on the User element and if I don't set
that when adding the domain user to a local group, installation fails.
I had looked at USERDOMAIN initially but that gets set to the local machine
name when you are not logged in as the domain user. But, I suppose I
Some more info. The problem seems to go away if I move RemoveExistingProducts
to after
InstallInitialize. I currently have it before CostInitialize, because
otherwise downgrades don't
work properly.
Rob
On 12/07/2010 09:28, Rob Hamflett wrote:
I've got a customer reporting installation
If you can't make it work with the wix extensions, take a look at
http://msiext.codeplex.com. The local group extensions don't need an explicit
domain property for the user - you can specify .\user, user, machine\user,
domain\user, u...@domain, etc. There's also a custom action to retrieve the
On 7/12/2010 8:17 AM, Rob Hamflett wrote:
Some more info. The problem seems to go away if I move
RemoveExistingProducts to after
InstallInitialize. I currently have it before CostInitialize, because
otherwise downgrades don't
work properly.
There are four supported schedulings of
How do you get Windows Installer to perform a downgrade? I find that if
RemoveExistingProducts
comes after costing, then the current files get removed and the new files don't
get delivered.
Removing the existing product removes the existing files, which affects the
actions the installer
There is also http://wixcontrib.codeplex.com that has a couple small
extensions. Contributions are welcome there as well.
On Mon, Jul 12, 2010 at 3:33 AM, dB. dbl...@dblock.org wrote:
This isn't quite as magical as it sounds. I think your problem is that you
think that you're REbuilding the
Hi
I have a custom action in C# that only put a value in a property
session[VALIDATEUSER] = 1; or session[VALIDATEUSER] = 0;. The
purpose of that CA is to check if a username and password provided by the
user is valid. If only using 0 and 1 now to do some testing. I have a dialog
that can call
Unfortunately, *I* personally don't know how to do dcomcnfg.
The ComPlus Extension,
http://wix.sourceforge.net/manual-wix3/complus_xsd_index.htm,
might be appropriate here but I don't know the details of its usage. Perhaps
somebody more knowledgeable can provide some guidance.
Edwin G. Castro
Hi,
Its a simple one, I can give you mine.
I'm doing some test with it. Nothing too complicated.
Hope it can help you
Rick
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5284348/SetupWIXTest.rar
SetupWIXTest.rar
--
View this message in context:
When supporting downgrades, set the REINSTALLMODE property. Specifically,
out of the following set of letters, you want either d or a: a, c, d, e, o,
p. Thus, a good value to use would be amus.
-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: Monday, July 12, 2010 6:29
I am new to WIX and have been tasked with creating an installer that does
the following:
*Deploys a build of our application without overwriting the App.Config file
for the application
*Loads the key/values in the App.Config file and prompts the user with the
defaults (existing values) and
How do I get the reference to automatically set the version number?
Thanks - dave
David Thielen - CTO/founder
303-499-2544 x1185
720-352-0676 (cell)
www.windwardreports.com
World's coolest blog - Windward Wrocks!
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Thanks Rob. I'd love to contribute. Where do you need more eyes?
As for the compiler extension, I'm back to where I was. I haven't been able
to get Candle to recognize the embedded wixlib in my compiler extension.
Experimenting with several ideas, I've added the Link element to my build
script,
I've got an update. I've gotten my wixlib to show up in my MSI! The trick,
for me, was to add a Property to the Fragment in the wixlib I was embedding
and then use a PropertyRef to pull it in in my installer project. Pulling
that in pulled in all the other stuff (including custom actions) from
When you add rows to your table, do you make a reference to one of the items
in your wixlib? That is usually needed to cause the appropriate fragments to
be included when your schema is translated into table entries.
The usual way is in your C# code use the CreateWixSimpleReferenceRow()
method on
Dialogs read values from the UI session. If the custom action runs in the
InstallUISequence then the properties will be available. If the custom
action runs in the InstallExecuteSequence, then those properties will not be
available to the dialogs, since properties only flow from the UI to the
GetLibrary simply adds the library to the other compiled wix code that light
uses to link. There has to be some reference from somewhere for light to not
throw out the fragment as unreferenced. That is the reason most compiler
extensions use CreateWixSimpleReferenceRow to create references to
Hi Folks,
In my installer I have serial key specific to the PC software been
installed. for validation purposes use has to send that key to us and
obtain a verification key. both keys are 32 characters long. hence
they are hard to type manually and best is to copy and paste.
I would like to add
Hello,
I have started to use WiX 3.0 to begin our transition away from
InstallShield. I really like using it.
I have a question that may or may not be obvious...
We have a requirement to get a list of registry keys under a parent key,
and display information to the installer. There is a
Ah, fantastic. That sounds like a much more elegant solution that using a
PropertyRef. Thanks Blair. So, it looks like this method is referencing a
table and row that would be created with the wixlib. Like this from the Util
extension.
core.CreateWixSimpleReferenceRow(sourceLineNumbers,
25 matches
Mail list logo
