Hi everyone,
I'm new to Wix, and got misunderstood about the behavior of util:RegistrySearch.
The following code is from a project, and detects if Visual Studio Professional
is installed.
I have installed Visual Studio 2012 and update 2.
But the Problem is that the required registry key do
https://lists.sourceforge.net/lists/listinfo/wix-users
It's appended to the end every single post to the list. Even your own & this
reply.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the
FYI I bug reported this back in August 2012 ->
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=3557976&group_id=105970
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Inte
Hi,
To prevent CustomActionData to be logged you should add
*msidbCustomActionTypeHideTarget
*(8192) attribute to CustomAction attributes.
To read CustomActionData you should create property in the following
format: PROPERTY1=VALUE1;PROPERY2=VALUE2;;PROPERTYn=VALUEn.
Then you read it like this
Hi,
This cannot be achieved without overwriting default behavior. You may
create Custom Action of Type 51 (set property) and set REINSTALL property
to the feature you want to upgrade.
For example: you have two features in your package: Feature1 and Feature2
that have one component attached to both
Good afternoon,
Got an issue with a third-party component. It's got its assembly set as
"global" and it wasn't getting included in my setup-package. I set it to
"local" instead, thinking it'd fix it. However, it didn't end up in my
"bin"-directory in spite of that, so I guess no surprise that
http://iranmama.ir/wp-content/themes/toolbox/flickr.php?ngftfv865llb.htm
briancovington
Brian C
-
Direct action produces direct reaction.
--
Hi,
I'm facing a .NET installation issue. My installer bootstraps .NET 4 installer
by using this:
It works great. But I just found it doesn't work for a disconnected computer.
The error log shows that my installer is trying access the Microsoft site to
download the .NET standalone ins
If you check the net fx extension that is provided with wix you can see that
all the options you can choose for the intall of the NET 4.0 need to download
the package from the web, even the full version.I hope that they could add even
this possibility, now the only way that I have found is to ad
Classification: Public
Sigh,
This is what I did but my SQL Server database password is STILL showing up in
the MSI log file, what is weird is that the deferred custom actions that are
called in the Product.wxs are hidden, but the deferred custom actions in my
merge module are NOT...
Product.wx
The product version number I have to use has the following form:
3.5.6.257832 obviously the candle compiler doesn't like this; is there any way
to suppress the error or to work around this limitation?
If I can't find a solution to this problem we are going to have to abandon WIX
in favor of a s
Correct me if I am wrong, but the VERSIONINFO resource can't handle numbers
larger than that.
(http://msdn.microsoft.com/en-us/library/windows/desktop/aa381058(v=vs.85).aspx)
-Original Message-
From: Rod Horsley [mailto:rhors...@control4.com]
Sent: Thursday, June 20, 2013 12:16 PM
To
We use the Inno installer for a different product and it has no problem with
this version numbering system, it however has file version and product version
fields...
The file version field is constrained but the product version field is not...
Later, Rod
/B^)
Rod Horsley | Software Engineer
Windows Installer might copy the version info model, but the limitation is
the ProductVersion property, and that's not a WiX limitation, it's Windows
Installer.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370859(v=vs.85).as
px
So "abandoning WiX" means abandoning Windows Installer
If this is the same general issue as previously, it's that custom action
code that creates ita own log entries can do anything it wants, including
writing properties you have marked as hidden in the MSI file.
It may help to post the relevant log entries.
Phil
-Original Message-
From: S
"Users can unistall and reinstall the same MSI right...?"
If that's exactly what's happening yes, you can do that. You install the
product, then uninstall it, then install it again. There's no problem with
that - it happens all the time. (You can't install an MSI and then
re-install the exact sam
Classification: Public
Solved...
This is an issue with Merge Modules, moved the deferred custom actions that
have passwords from the Merge Module to the Product.wxs!
Is this a MSI issue or a WIX issue? (seems and doesn't work in Merge Modules :(
Steve
-Original Message-
From: Steven O
>From the looks of it; I may have no choice but to abandon the Windows
>Installer in favor of a more robust product...
Thanks for your time and your feedback...
Later, Rod
/B^)
Rod Horsley | Software Engineer
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: T
On a 64 bit machine the key is at:
HKLM\SOFTWARE\Wow6432Node\Microsoft\DevDiv\vs\Servicing\11.0
So I wonder if when you indicated that it succeeded if it actually found the
key under the 32 bit registry node and you checked under the 64 bit node
which does not have the relative path of .\vs\Servi
Anyone out there have any ideas about our problem below?
I'm thinking anyone with experience using WiX or the Windows Installer with JSL
or a Java-based service are best positioned to know how to solve this.
Alain
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Jun
Hi Marco,
I'm kind of new to WiX. Where is the "net fx extension" that you mentioned? Is
it just a XML? I'd like have a look at how they do the detection so I can clone
the piece in my local package approach. Thanks!
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sen
I'm using difx to install a handful of drivers in a single msi. The
installation works great. However, when I uninstall the msi it appears to
only remove my driver package and not issue a proper uninstall. I can
tell because my class installer that complements my driver is not getting
called
Such things outside MSDN specs are very risky! If anyhow possible try to
avoid them. E.g. we got issues (afair FindRelatedProducts) as our version
number was 4.451.. when migrating to Major 5. We then needed to use
think it was 5.195.. instead of 5.1...
And IMHO 255.255.655
Remember, Merge Modules modularizes all identifiers.
On Thu, Jun 20, 2013 at 12:13 PM, Steven Ogilvie
wrote:
> Classification: Public
> Solved...
> This is an issue with Merge Modules, moved the deferred custom actions
> that have passwords from the Merge Module to the Product.wxs!
>
> Is this a
Personally, I wouldn't use the word "robust" in that sentence. The word
"flexible" may be appropriate but not "robust". The alternative
installation engines available on the Windows platform are not more
"robust".
On Thu, Jun 20, 2013 at 12:21 PM, Rod Horsley wrote:
> >From the looks of it; I m
25 matches
Mail list logo
