if you install N followed
> by N-1, the N-1 COM component will be the one being used (assuming the
> COM ID didn't change).
>
> Your choice will depend on which restrictions cannot be removed.
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedtyp
What are the implications of two files having the same component GUID
but different key paths in different installers?
Some background:
* Release N-1 has a COM component with component guid G and the key
path COMDll${N-1}.dll with related registry keys as part of the component
* Release N ha
On 10-09-10 7:41 PM, little.forest wrote:
> I don't know how to use batch file in customaction.
The same way you'd use any other command. I gave you an example!
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbuc
mmand
(iirc). So something like:
The batch file can use %~dp0 to change to the installdirectory first.
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket.org/cheez
On 10-09-08 12:06 AM, Sohail Somani wrote:
> Hi,
>
> My installer launches the app upon installer completion (well, the last
> wizard page.) By this point, a required environment variable (PATH) does not
> seem to have been set as the new process gets the old version.
>
> Th
orrectly? The file is not
> read only (it was locked by source control the first time I added the new
> assembly reference).
>
Heat needs to be able to load the assembly properly. Are there
dependencies missing? Adding the dependencies to the PATH variable
worked for me.
--
. Is there a way to ensure that the custom action is launched
with the new environment?
Thanks!
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket.org/cheez
On 10-09-05 8:05 PM, Sohail Somani wrote:
> Hi there,
>
> Is there a way to see why Windows might start MSI repair automatically?
> Perhaps run some kind of integrity check on installed packages?
>
> I've got an issue with some shared files between application versions.
&g
On 10-09-05 8:05 PM, Sohail Somani wrote:
> Hi there,
>
> Is there a way to see why Windows might start MSI repair automatically?
> Perhaps run some kind of integrity check on installed packages?
>
> I've got an issue with some shared files between application versions.
&g
seems
to be some kind of issue upon uninstalling the later version.
Suggestions on how to debug would be helpful!
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket
oment though.
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket.org/cheez
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel progra
r the first one?
I had this problem when heat could not load the DLL due to missing
dependencies. If your component depends on something in another
directory, you should add it to the path.
Not sure if that is the correct solution, but it was the one I found anyway.
--
Sohail Somani
--
iBlog
can this be done automatically using heat.
>
Generally, it is recommended to use the heat output as a starting point
but you can use a scripting language for this too.
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisof
something else like 1.0.0 into the
> Version attribute.
>
> If you try to work around the version numbering scheme, you might run
> into difficulties with Upgrades which require versions to be comparable.
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedty
aranteed to cause me problems. Is there a
simpler way to exceed the limits without using VB script? Should I write
to the registry manually?
Thanks.
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http:/
Thanks, this clarifies perfectly.
On 10-08-24 5:48 AM, Peter Shirtcliffe wrote:
> http://robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-
> would-you-use-them
>
> -Original Message-----
> From: Sohail Somani [mailto:soh...@taggedtype.net]
> Sent: 23 Augu
t; SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedtype.net]
> Sent: 21 August 2010 06:11
> To: wix-users@lists.sourceforge.net
> Su
Oh, I'm trying to keep it simple here :)
On 10-08-20 4:14 PM, Blair wrote:
> Or, alter your upgrade table to something that allows whatever your SxS
> story is.
>
> -Original Message-----
> From: Sohail Somani [mailto:soh...@taggedtype.net]
> Sent: Thursday, August 19,
to:os...@live.com]
> Sent: Friday, August 20, 2010 1:12 PM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: RE: [WiX-users] Shared files/registry question
>
> wixlib
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedtype.
mponentRef.
Whether the above is right or wrong, could someone please enlighten me
as to the least headache-inducing way to do this properly with WiX?
Thanks in advance.
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket
ons side-by-side, you
should use a different UpgradeCode for each major version, correct?
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket.org/cheez
--
s 7.
>
> Has anyone noticed similar behavior?
>
> What could be causing this problem?
Alpha channel?
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket.org/cheez
---
Thanks!
On 10-08-12 5:37 PM, Blair wrote:
> If you are using MSI 4.0 or later, you can add the MsiLogging property to
> the Property table.
> http://msdn.microsoft.com/library/aa370322.aspx
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedtype.net
Thanks. So I guess there is no command in Windows Installer to generate
a log file?
On 10-08-12 11:15 AM, Michael Clark wrote:
> See
>
> http://support.microsoft.com/kb/223300
>
>
> -Original Message-----
> From: Sohail Somani [mailto:soh...@taggedtype.net]
> Sent: T
This is probably a MSI question more than a WiX question but here goes:
is it possible with WiX to always generate an install log without
requesting it on the command-line?
Thanks!
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http
re-release
> build getting left behind.
>
> Many people also use this table to implement downgrade protection.
>
Ah, thanks for the helpful tip. Simplifies a few things!
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbuc
cally, here are the relevant sections of my wxs file:
Does this sound like a silly, dangerous thing to do or am I a genius?
Thanks in advance.
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitte
p://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5
Gotcha, thanks.
Turns out I do not need to install prerequisites so I'm very happy! :)
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somaniso
the code for it anywhere!
--
Sohail Somani
--
iBlog : http://uint32t.blogspot.com
iTweet: http://twitter.com/somanisoftware
iCode : http://bitbucket.org/cheez
--
This SF.net email is sponsored by
Make an app they can
29 matches
Mail list logo