I'm new to Wix. I'm trying to make a installer for website - something
similar to what visual studio IDE provides.
I've tried using the two scripts mentioned in the posts here to populate the
combo box with the websites available on a machine as well as set the port
of the in the WebAddress
Hello everybody...
I started to use wix a few days ago and also there are some great
tutorials and howto's out there I wasn't able to find answers to all my
problems...
The application I try to write an installer for has got a config file.
I'd like to install the default config only if
Hello there setup Gurus..
I'm thinking of using WiX v3 for my new setup project.I was using v2 for my
just completed project..
Can anybody tell me how reliable is v3 compared to v2?..Do i have to unlearn
any v2 learnings? can i give it a shot with my experience in v2?
I have to take a call on
Hi
I've been running into a problem which I haven't been able to solve
related to vista and uninstalling. I have a package which is set to
install per-machine and elevated, which requires the user to be
administrator to install the package. Under windows vista when the user
is the computer
I'm using WiX 2 and DIFxAPP that ships with Vista WDK.
Application to install is a KMDF class filter driver.
I have written an INF file that describes that my driver uses WDF. But
DIFxAPP won't see that and installs only driver files ignoring
WdfCoInstaller.
Where is the error? There are INF
Our team ran into the same issue last year, the problem appears to be a
bug in msiexec for Vista (and Longhorn). You will probably have the
same problem with the Repair and Modify options as well, at least we
did.
Our solution/hack was to create a small executable that elevates the
privilege
Javier Liceaga wrote:
Our solution/hack was to create a small executable that elevates the
privilege that then calls our msi.
Thats what we're planning on doing for future releases where we require a
bootstrapper, however, for the next release I wanted to fix this only using
the msi
What are some of the best practices for authoring the installation of
COM components? Obviously, I know selfreg is evil. When it comes to the
registration of COM components, should you author the registry entries
within the same Windows Installer component, or as separate components?
I've argued
I, personally, absolutely love WiX v3. I have a bunch of installations built
with WiX v2; I took a couple of 'em and moved them over to WiX v3 (with very
little problems, I might add).
Moreover, a bunch of the features within WiX v3 actually saved me time and when
I re-factored, was able to
Removing -delta option from Pyro's command line gives me the same
result: it reports that no files are added to the patch cab. I'll need
some time to try with changing the third version number since I'm doing
tests on actual builds, not a toy system.
I find it interesting that MSP built with Pyro
I am writing an installer for an IIS7 Virtual Directory.
I want to use Anonymous Authentication, and have IIS use the Application Pool
identity to access the files. Is there a way to do this with WIX?
Details:
I have
WebDirProperties Id='ReadAndExecute' Read='yes' Write='no' Script='yes'
What is the best way for a WiX v2 built installer to test if one of the
standard Windows Server 2008 Features is installed? Is it possible for
an MSI file to invoke the installation of a Feature before continuing
with the rest of its own installation?
I need to check if a Feature is installed; if
WiX v3 is relatively close to v2 in syntax. There are a few things which
have been updated to make things simpler, but overall really it's not a huge
change. Certainly I think you'll have a pretty easy time learning anything
new that's necessary. Stability for me has been for the most part pretty
Hi guys,
I am trying to use the SqlDatabase and SqlScript elements to install a
database and run some scripts to generate stored procs and tables etc.
What I would ideally like is the user to be able to specify the database
name in the setup UI, and then use that within the scripts.
The
I'm creating a user (ServiceUser) as well as specific folder permissions
during my install for ServiceUser. When I run the uninstall though,
ServiceUser is removed, but it appears the permissions that I've created
for ServiceUser are still there. I say appears because (after a restart)
the user
Sorry forgot to mention I am running the latest WiX version - 3.0.4318.0.
And SQL 2005 if that makes any difference.
Hi guys,
I am trying to use the SqlDatabase and SqlScript elements to install a
database and run some scripts to generate stored procs and tables etc.
What I would ideally
There is not anything built in to Wix right now that will let you use
variables in SqlScripts. You can load them into SqlString elements and use
the normal [property] syntax.
You can build a CA that will do this as well, which is what I did.
Good luck!
Chris
On Thu, Aug 7, 2008 at 5:01 PM,
Hi,
I have the following issue. On uninstall, all files are removed, but the folder
structure remains.
- The only file that stays in the folders is an InstallLog file written
by the InstallUtil.exe (it is executed as part of install against one of the
component's dll's). could creation
Greg,
This scenario I've used in
http://blogs.technet.com/alexshev/archive/2008/07/01/from-msi-to-wix-part-19-the-art-of-custom-action-part-1.aspx.
You don't need all that custom action stuff. Search for RemoveFile in it.
Regards,
Alex Shevchuk
-Original Message-
From: [EMAIL
Nic, what I've been doing is using the sql:sqldatabase as an anchor outside a
component with master as the target database (since it's guaranteed to be
there and any authenticated user is guaranteed to be able to connect to it),
then I use the sql:sqlstring to restore the database from a
I'm trying to figure out the best way to patch our product using the new
Wix patching method or using the PCP/PatchWiz method.
Right now I'm trying to accomplish everything using the new Pure Wix
patch method. I'm using the patch samples from the Wix help file for
testing.
My goal right
Hi,
When we released the RTM of our product (our first experiment with Wix), we
included a launch condition to ensure the program wasn't already installed:
Condition Message=An existing version of [ProductName] is already
installed. Please go to Add/Remove Programs and remove it before
22 matches
Mail list logo
