Hi:
is serial number validation built in to wix via a dialogue, or would I have to
create my own?
Regards
Sean.
--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for th
Hi,
If we delete the MSI from disk after install, Repair option fails with the
message "The feature you are trying
to use is on a network resource that is unavailable".
How to enable local cache in Wix?
This feature works on InstallShield created BasicMSI projects by default.
thanks,
Vivek
---
Switching the TFS Build 2010 process to 32 bit indeed solved the
issue. No more exceptions. Now the issue is that its MSBuild 4.0 and
TFS Build 2010 is building the .wixproj before the .csproj it is
referencing. That is not going to work right. However, that is going
to have to be a new thread
Not done this myself but I note there's a section on it in Nicks WiX
book (available from PacktPub.com) which I got last week and just
starting to read :)
On 10/29/2010 03:40 PM, Tom Crozier wrote:
> I have searched the web and have tried playing around with adding billboards
> to my installer
I have searched the web and have tried playing around with adding billboards to
my installer but have not been successful. Does anyone have a tutorial or
example on how to accomplish this?
Thanks- Tom
--
Nokia and AT&T p
Perhaps this isn't the right forum for this. I am using Visual Studio 2010
and WIX 3.6. If I have a wixproj loaded and I get errors, I used to be able
to double click the error and go right to the line (like any normal IDE).
It isn't happening with VS2010. Does anybody else have this behavior?
Thank you so much removing that worked.
From: Nick Ramirez
To: wix-users@lists.sourceforge.net
Sent: Fri, October 29, 2010 6:22:31 PM
Subject: Re: [WiX-users] Deploying File in GAC
Do you need the AssemblyApplication attribute? I've not used that before when
Hi
I have a WSP which has to be deployed using the WIX installer. I am right
now deploying this by running a batch file which deploys this WSP and activates
the feature. And during uninstall will run another batch file which will
deactive the WSP and uninstalls it. Would like to know if this is
Hello Nick,
Replies below...
> You shouldn't ever need to change the UpgradeCode as long as it's all the
same product. Windows Installer needs the UpgradeCode to stay the same so
that it can detect older versions of itself during an upgrade,
> should you ever set it up to do one. For example, t
You shouldn't ever need to change the UpgradeCode as long as it's all the
same product. Windows Installer needs the UpgradeCode to stay the same so
that it can detect older versions of itself during an upgrade, should you
ever set it up to do one. For example, the Upgrade element needs that same
c
When you change a components key (directory) path, you should change the
guid.
Using * for the GUID generates a GUID based on the key path (file name
and location or registry path). Sounds like just the thing you need.
-Original Message-
From: John D. Marinuzzi [mailto:nu...@hypack.com]
S
Do you need the AssemblyApplication attribute? I've not used that before when
installing to the GAC.
-
Learn WiX with the book:
https://www.packtpub.com/wix-a-developers-guide-to-windows-installer-xml/book
WiX: A Developer's Guide to Windows Installer XML
--
View this message in context:
Hello All,
Our company puts out a release of our software once a year. By default, it
gets installed in a directory that is unique every year. I just started
using WIX last release and we have a new one coming up. Our customers will
often keep the old version during a transition. My question
HI
How to deploy a file in GAC using WIX? This is what I am using but no luck L
Regards
Anweshi
--
Nokia and AT&T present the 2010 Calling All Innovators-North America
Not specifically a WiX issue, but perhaps relevant.
According to the MSDN for the ControlEvent table, both Event and Argument
are of type Formatted.
Column Type KeyNullable
EventFormattedY N
Argument FormattedY N
However, testing seems to indicate tha
I am working on a project that makes use of setupbld from Wix 3.0 to build a
bootstrapper (even though we use Wix 3.5 to build our MSIs). We don't chain
MSIs or install pre-requisites. We use a bootstrapper for UAC compatibility.
For this limited purpose, setupbld works OK.
In order to help with i
The WiX bootstrapper "Burn" is in development for v3.6. Until then you
can either use something like dotnetinstaller
(http://dotnetinstaller.codeplex.com/), SharpSetup
(http://sharpsetup.eu/) or a commercial package.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
Thanks Sandher for your reply!
I searched google and didn't get very well what the bootstrapper is. Is it a
program that start different .msi(in my case)? Do you have a code snippet
(c#) so that i could learn a little? How is it (bootstrapper) meant to be
work?
--
View this message in context:
h
Hi.
On Thu, Oct 28, 2010 at 10:40 PM, Nick Ramirez wrote:
>
> You shouldn't need to schedule the MigrateFeatureStates action manually. The
> UpgradeVersion element has an attribute called MigrateFeatures that you can
> set to "yes".
Thanks a lot, that did the trick. My bad - I noticed that the f
19 matches
Mail list logo
