Hi John/All,
I have used the below commands:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag -dr
TORTDEMO -out trunkdb.wxs
candle TortEngineDemo.wxs trunkdb.wxs
light -b D:\Project\ESI\Code\trunk\db -out TrunkDBDemo.msi
TortEngineDemo.wixobj trunkdb.wixobj
This does create the
That should have read:
If you make this change, you can also remove the following line:
RegistryValue Root='HKCU' Key='Software\[Manufacturer]\[ProductName]'
Type='string' Value='' KeyPath='yes' /
On 19 November 2013 08:34, John Ludlow john.ludlow...@gmail.com wrote:
That's because of this:
That's because of this:
Directory Id='DesktopFolder' Name='PFiles'
This will put files on the users desktop - are you sure that's what you
want? (Hint: it's probably not) Change this to ProgramFilesFolder (or
ProgramFiles64Folder). Remember how you were getting a similar error
previously?
Hey!
I have windows program installation bootstrapper project. There is .NET
framework, Visual Studio C++ redistributable, device driver installer and my
application installer in chain:
Chain
PackageGroupRef Id=Netfx45Xxx/
ExePackage Id=CppRedist
In the log file below, you canceled before it would have shown the command-line
that would have been launched. It seems like things should be working.
-Original Message-
From: Michael Kolowicz [mailto:michael.kolow...@km-f.eu]
Sent: Tuesday, November 19, 2013 2:43 PM
To: 'General
Thanks for clarification, but I do not understand anyway how to elevate the
uninstall. Should I always use my setup.exe to uninstall the app instead of
add/remove programs?
Понедельник, 18 ноября 2013, 17:05 -08:00 от Phil Wilson
phildgwil...@gmail.com:
On UAC systems a check like the one you
Hi John,
Thanks for the help...Just followed the steps...worked like a charm. The
folder got installed into the program files folder and there were no
errors thrown by Light.
But I want the db directory to be created into a folder in say
c:\[FolderName](c:\[FolderName]\Tort Demo). I have
I have found a way to elevate my msi. The solution is to use
InstallPrivileges=elevated in Package and do not use setting
MSIUSEREALADMINDETECTION property.
Package Id=*
Description=Description
InstallerVersion=301
Compressed=yes
InstallPrivileges=elevated
InstallScope=perMachine
In theory, just removing this line should do it:
Directory Id='DesktopFolder' Name='PFiles'
I haven't tried that though, so I'm not 100% sure. If not, you can also try
a custom action which sets the directory.
Generally, you should think twice before dropping files directly under c:\
-
Ok, I have made the following changes to the TortEngineDemo.wxs(also
they are attached):
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='MyFolder' Name='EnergySolutionsInternational'
FileSource='D:\'
Directory Id='TORTDEMO' Name='Tort Demo'
Component
That looks like expected behaviour to me.
What's happening here is that the installer's created that directory
structure and deployed a bunch of resources. During uninstall, it
determines that those are the files it deployed and removes them. you can
specify Component/@Permanent=yes if you want
Feature request is open for engine to do this. Something like Restart
Boundary. BA can always force restart on completion of a package during
execution.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, November 19, 2013 6:41 PM
To: wix-users
2013/11/19 Joe Dimagio joedim...@gmail.com:
Hey everyone,
I'm doing some research to see if WiX is right for my corporation to use.
Reading the MS RL, it looks like if I distribute my product using WiX, I
need to include my source files including the wxs, wxl, wxi, wixproj, as
well as my
http://wixtoolset.org/about/license/
-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com]
Sent: Wednesday, November 20, 2013 6:48 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Microsoft Reciprocal License explaination
2013/11/19 Joe
The problem is the way they say normally not included. Got to love lawyers.
FWIW, I get into grey areas with my tool IsWiX. Include very small pieces of
WiX in my solution ( mainly the use of Microsoft.Deployment.WindowsInstaller,
the inclusion of schema (XSD) files for validation
If one does not claim the WiX code as part their own stuff (i.e. all the
copyrights are left in place) and one does not change any code (i.e. WiX code
is same as code published on WiX toolset site) then from my understanding
(you'll need to get your own lawyer) they are still complying with
But if I change something in the WiX toolset and don't distribute the
modified WiX binaries (I only distribute msi packages generated with
the modified WiX), I don't have to distribute the source code to my
modifications, do I?
--
Nicolás
2013/11/20 Rob Mensching r...@robmensching.com:
If one
Hey John,
Thanks for all the help you provided to me on my issues. I do not
currently have this book but would get it ASAP(ebook)
Thanks once again and look forward to your guidance.
Regards,
SuvraJyoti
On 19-11-2013 16:29, John Ludlow wrote:
That looks like expected behaviour to me.
What's
Depends on which lawyers you ask but I'd still leave you with my last comment:
Your stuff is yours but don't steal from the community.
If you improve our stuff, give back.
-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com]
Sent: Wednesday,
19 matches
Mail list logo
