Well spotted Nicolás. That was indeed the root of the problem. That and a
syntax problem with the command line params and where in the install execute
sequence it was scheduled to run.
I ended up with...
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
I am new to WiX and I've been trying to use it to create a installer for a
basic console application which just prints hello world in console and
hangs there. My question is, can WiX be used to create windows service for
any console application?
I know that it can be used to create service
You probably don't have sufficient permission. Try running your MSI as
Administrator.
On Jul 9, 2014, at 7:19 AM, Pritesh Acharya priteshacha...@gmail.com wrote:
I am new to WiX and I've been trying to use it to create a installer for a
basic console application which just prints hello
Thanks John, but yes I have seen that article and it still does not explain
how you can enter 1 to 5 numbers in the field.
If I change enter 1, 11, 111, the next but will fail to do anything,
but if I enter 1 then the install will proceed as expected.
So it seems that if the text field
As the last comment in the article suggests, you'll probably need a custom
action to pre-process the data and decide if it's any good. It would be nice
if MaskEdit took a full on regex, but it doesn't in WinForms either.
Bummer.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack
A console application is not a windows service, unless it implements code to
support the windows services API. The error indicates that the SCM sent an
event to the service and it did not respond (which makes sense if it was
just a console app and did not have any code to support the windows
http://buildmaestro.wordpress.com/2011/08/30/c-dtf-using-locale-net-culture-folder-and-resources-files-for-translations-with-makesfxca-exe/
--
Open source business process management suite built on Java and Eclipse
Turn
I have a project that has a large number of files. Between versions of our
software, new files get added and some get removed. Therefore, in
automating our build process, I would like to have heat auto-generate a .wxs
file (let's call it files.wxs).
But then there are certain hand-generated
Sounds like you need to give a component group name in your heat call
-cg MyComponentGroup
Add the wxs file generated from heat to your project.
Add the a ComponentGroupRef to your feature or another componentgroup depending
on your preferences to the hand rolled wxs file.
Done
-Original
Hi, I am currently validating the app using the Windows App kit certify. It
looks like I have to get rid of a warning which says:
Program fails due to missing install location.
Native apps e.g. 32 and 64 bit must be installed to the %ProgramFiles%
folder by default, note that 32 bit apps
That sounds like the install location is missing in the ARP entries,
and you can set that in each MSI by setting the ARPINSTALLLOCATION
property to the value of INSTALLFOLDER (if that's what you're using)
after the location has been chosen.
Burn should simply be installing packages, commonly MSI packages. For a single
MSI, it has to have its bitness set as either 32 / 64. Windows Installer will
do the proper folder redirection for you.
In your case, I would think you would have a single bundle, with two (or more)
MSI packages.
I am in the same situation.
The last warning that you are mentioning, InstalLocation is missing, if you
compare both entrance in the registry values
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}
and the one in
Thanks, scubasteve2! That got me through my current error and led me on to
my next. I'll go ahead and post that as a separate question, though.
Thank you so much!
scubasteve2 wrote
Sounds like you need to give a component group name in your heat call
-cg MyComponentGroup
Add the wxs
The util:FileSharePermission element has many attributes for setting ACLs on
a file share, but none of them seem to work except for GenericAll. For
example, the following code will not give the user the specified
permissions:
Component Id=cmpFileShare Guid={6974184A-1F4F-4FBB-ADA6-826E9C947A7C}
Okay, I was wrong! I guess by setting only Read permission on the folder
(using Read, GenericRead, and ReadPermission -- not sure yet which one is
the magic one), the user is able to read the files in that folder and cannot
change/modify them. I guess it works even though the checkboxes for Read
16 matches
Mail list logo