Hi all!
Need help. Some msi's have been distribured in Windows domain over GPO as
per-user installations.
Now I need to upgrade them, upgrades are per-machine (this is better for my
purposes).
What is proper way to uninstall old applications?
Seemed like I can't to upgrade them via Wix code an
Given the contents, you appear to be referring to the example either at
http://blogs.msdn.com/b/pmarcu/archive/2007/06/28/sample-patch.aspx or
http://wix.sourceforge.net/manual-wix3/wix_patching.htm . The reason you aren't
providing a product or upgrade code is because you are providing the wixp
I just wanted to ask that what PATCH keyword means? Upgrade or Patch?
What condition I choose if I want to display upgrade UI on upgrade as most
of the places I have seen:
NOT Installed AND NOT PATCH
Installed AND PATCH
What should I use in case of Upgrade (there is no patch in my case)?
--
Than
Hi,
Thanks for your pointers.
What I am confused with is that the code shown to create the Patch.wxs does
not contain the product code or upgrade code at all
http://schemas.microsoft.com/wix/2006/wi";>
http://www.dynamocorp.com/";
DisplayName="Sample Patch"
Description="
Done :)
Bug id: 3536160
I took a quick look at the log '
WiX_Toolset_v3.6.3014.0_20120619113652_3_nsdk2005.msi.log' and found this
message right near the end:
MSI (s) (54:D8) [11:41:16:257]: Product: WiX Toolset v3.6 Native 2005 SDK --
Installation completed successfully.
So, does this mean
Hmm, sounds intriguing. Could you point me in the direction of some more
information about this approach and/or provide an example? The WiX docs
mention binder paths in "How To: Specify source files", but I wonder if
there is more thorough source of information.
Thanks again for your advice!
_
hi -
i've written a dll which hits a REST api that my app needs to hit to
register its existence with the server, but for some reason or another it
seems that my dll is not being hit. i've built a simple exe that links
against the dll and that exe works, so i know my dll works at least when
linked
Something else to consider: instead if using loc variables, try organizing
your build location so that bind paths can be used. Then when building you
can provide the appropriate bindpath on the command-line. I do this to
minimize the File/@Source elements all the time. "Named base paths" can be
qui
Jens,
I believe a component condition using an ampersand (&) for the action
state of the features should be sufficient. Taking a look at
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx
(Conditional Statement Syntax), the WiX code would look something
I think that I may have caused some confusion by naming the File/@Id field
the way I did in my example. In reality, I am using "heat"-style ID's (for
example "filB75B712DC4A64A7882230FE0BCC0CC3E") for all of my files.
Regardless of the ID convention, though, I get the same errors.
However, I did j
Instead of specifying File/@Id, try specifying File/@Name. I think the
issue is that the File/@Name is defaulting to the value from File/@Source.
By specifying File/@Name you are telling the WiX toolset the explicit file
name to use for the install. File/@Id will default to File/@Name giving
you t
Nope, not yet. Feedback was to not cut it. It *should* work but I haven't
personally tried lately. Can you provide the WiX toolset install log from
your %TEMP% folder and put the information in a bug to track the issue?
On Mon, Jun 18, 2012 at 7:25 AM, Christopher Painter wrote:
> I seem to recal
The WiX tutorial at http://wix.tramontana.co.hu/ is accompanied by a few
samples, the simplest of can be found on the "Putting it to Use" page (
http://wix.tramontana.co.hu/tutorial/getting-started/putting-it-to-use).
The direct download link is
http://wix.tramontana.co.hu/system/files/samples/Samp
I seem to recall that suppor for 2005 was dropped a couple years ago.
http://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5
From: "Naim Kingston"
Sent: Sunday, June 17, 2012 9:37 PM
To: "wix-users@lists.sourceforge.net"
Subject:
Hi,
I want to know that is there any link from where i can download a simple
Wix sample , make a wixobj on my system just to have a better understanding
of how the wix is made to use.
Thanks
--
Live Security Virtual Confe
I am authoring installer using Wix 3.6 RC. I am able to implement install,
uninstall, repair and rollback. I am only struck at Upgrade (mostly major
as my product does not support minor upgrades).
I implemented that basic upgrade but I saw some strange behavior. On
upgrade my installer runs Instal
Thanks, I suppose that solution could work.
Nonetheless, I feel like this should be a fairly common scenario and that
there should be some way to support it using the built-in localization
features. I think that this would be easy if either all of the localized
source files (in my example, the Fil
1. Create your first version of the MSI in VS.
2. Create a second version of the MSI in VS as a new project that implements
a minor upgrade (see MSDN if you need any help with that - basically change
the version number, but not the product or upgrade codes, and obey the
component rules).
3. The nex
I am also thinking this way but was not sure any other (better) way of
doing this. But thanks for your valuable suggestions.
On Mon, Jun 18, 2012 at 1:31 PM, Dirk Räder wrote:
> Hi,
>
> I'd take the usual way:
> Define some properties that hold the path to the registry key(s) and
> the desired v
Hi,
I'd take the usual way:
Define some properties that hold the path to the registry key(s) and
the desired value(s). Access these properties within your CA and you
should be fine.
This way, you can reuse the CA for more than one installer without
changes to its source code.
Kind regards,
Dirk
Thanks John. It worked.
On Mon, Jun 11, 2012 at 6:56 PM, John Cooper wrote:
> Make sure you have " on both ends of the absolute path to appcmd.exe.
> You're missing them in your code, and that will break everything. Also,
> you need to make sure: 1) that the property you're setting before the
Hi,
Thanks for your update, your response is helped for me.
I have three more questions.
1. I followed the below code to uninstall the installed msi file.
Managed code:
SyncBA.Model.Engine.Detect();
SyncBA.hwnd = IntPtr.Zero;
SyncBA.Model.Engine.Plan(LaunchAction.Unins
I want to store some registry value within the custom action. There are
some other registry I also write via WiX. Within Custom Action, I have to
get the path of registry key so that I can add a new string into it but I
am not sure what will be the best way to do so this.
Any suggestions??
--
Th
You could try doing this with variables instead of localised strings.
If there are a lot of these variables then you could put the command
line arguments for defining them into a file and add "@filename.txt" to
your command line, with a different file for each language.
Rob
On 15/06/2012 17:4
24 matches
Mail list logo
