I am creating a WiX installer, and have configured it to show a prompt when the
user clicks 'install' if the user is missing a certain file. I added this line
in order to link my custom prompt to the rest of my dialogs (My prompt is
called Custom_Cancel):
If the user is missing a certain
I am creating a WiX installer, and I want to allow the user to select the path
of the installation directory as well as a data directory. I added two
InstallDirDlg's to my code and named one Custom_Dir and the other
Custom_DirData.
In Custom_DirData, instead of using the WIXUI_INSTALLDIR propert
1) yes
2) you could
3) yes, you could but you would need to manually extract the dll in you managed
ca (after embedding it in the msi) and then pinvoke that dll. Fairly certain
.net requires the native libs to exist as its loading your assembly, so you
would need to build the reference to the n
Hi ,
I have installed our main Installer(msi) with administrator rights, now i want
to install the *.msp with Standard Users Rights(Non-administrator)
Thanks and Regards
Ravi Shankar
--
This SF.net email is sponsore
I would like do something like this:
CustomActions.cs:
[CustomAction]
Public static ActionResults MyCustomAction(Session session)
{
...
NativeMethod.XYZ xyz = new NativeMethod.XYZ();
}
NativeMethods.cs:
internal static class NativeMethods
{
Intern
For major upgrade case:
yes. The easiest way is to use generated component guids (when the keypath's
name changes (or the directory "chain" changes in the case of filesystem
keypaths) the computed guid will differ, and changing the guid means (from the
POV of Windows Installer) that you delete
> Burn is very self-contained and only uses files it carries with it, although
> a custom BA can do anything.
I'm not using any custom BA (that I know of). My Bundle source is below this
message, for your reference. Please let me know if you see anything wrong (or
don't see something that shoul
I have been following this thread, and while I am pretty new I decided to
play with this problem as a learning experience. I created the following
modules, which are slightly different from your code, which compile and do
not generate any warnings or errors. I think the main change I made was to
I think I was having similar issues, and I reverted to using
http://wix.sourceforge.net/manual-wix3/patch_building.htm It does have some
shortcomings
(http://blogs.msdn.com/b/heaths/archive/2010/08/24/comparison-of-patchwiz-and-wix-v3-patch-build.aspx
) , but it allowed me to create patches o
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Wix-3-5-Heat-Cannot-harvest-64-Bit-COM-DLL-Registry-Data-td7583833.html
http://sourceforge.net/p/wix/feature-requests/399/
The first is a reference to someone having a possible solution, the second is a
link to the feature request
Sounds like you need to write your own UX/BA. You shouldn't depend on a CA
"securing" an install, as there are several tools out there that would make it
easy to modify and remove said check. You could base your UX off of WixStdBA
(C++), or you could write a managed one (.Net). If you clone t
Thank you very much for the information. - Miaohsi
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Friday, June 28, 2013 3:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need heat.exe to include extra file source subfolder
I'm
I want to make an installer that lets the user enter a key, which is then
evaluated by a custom action. Depending on the result of this evaluation,
the installer should download a set of MSI's from a remote location and
install them with no further action from the user. As far as I know, in
order t
Great, I've been looking for version comparision for a long time.
I've updated the conditions (see below). This seems to work, but I
didn't do a lot of testing, yet.
http://go.microsoft.com/fwlink/?LinkID=253117";
DetectCondition='NOT VersionNT64 AND
Hi All,
Hopefully this is the correct place to post this..
I've currently got a 64bit win32 com component that requires registering via
regsvr32.exe
I've been reading that the correct way to use this in WIX is using heat.exe to
extract what will end up in the registry and including that in my
I'm still rather struggling with this
My own MSIs I can fix if needs be by not using an MSM however I still need an
MSM to supply to customers to include our redistributable component in their
own installers. I want to allow the MSM to be used in per-user and per-machine
installers.
In ord
Hi Guys,
we are using the way of building patches as described in WiX help "Patch
Building Using Purely WiX", meaning that we are building the delta from the
wixpdb's using torch.
The only difference to the sample is that the files for the different
versions are always in the same location during
17 matches
Mail list logo