Somebody is going to have to provide the site-specific information. The
question is how do you want to specify it. Are you in a position to provide a
small subset of your client a MSI package that has already been transformed? If
not, then the client will need to be responsible for customizing t
Hi Edwin, Dirk, and All,
Those are some interesting ideas to ponder. But I also think I should
clarify my situation. In my case, the issue isn't so much with
creating the site-specific transforms. That task is performed by
support staff proficient with the tools, and we have other reasons to
have
Hi Rob,
Is there an alternate solution to avoid this problem? I am stuck with a
similar problem and I understand it's the Windows Installer that behaves in
this way.
Thanks for your help.
-Hitesh
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ins
Thanks, Dirk. The installer is being executed on the target machine so it is
using the shared folder as the installation target that is the issue. I'm not
getting the user to enter that at runtime so I am using a custom action to set
it. Is that the best way?
-Original Message-
From: Di
2012/3/19 Paul Taylor :
> Hi,
>
> Another newbie question: I can find lots of references to creating a share on
> deployment but how can you deploy files to a share that already exists on the
> target machine?
>
> Paul
>
Hi Paul,
that depends on the machine on you're installing to :-)
If the i
I downloaded this weeks build, 3.6.2712 and I am getting this error building
my install project which currently builds with the 3.5 GA
Could not load file or assembly
'file:///C:\src\tools\shared\WiX\v3.6.2712\bin\candle.exe' or one of its
dependencies.
Operation is not supported. (Exception from
Hi,
Another newbie question: I can find lots of references to creating a share on
deployment but how can you deploy files to a share that already exists on the
target machine?
Paul
This message and its attachments are intended for the above named only. If you
See the setupexe C++ project code in the source distribution.
--
John Merryweather Cooper
Build & Install Engineer – ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Alec Swan
This is with reference to Re: [WiX-users] wixproj question. Is Votive expected
to support Wildcards in the future?
thanks,
Venkat
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p
Please disregard the question. I found out that my HeatTypeLibs property was
using invalid XML characters (not sure why since it was upgraded from
VS2008,Wix3.0 to VS2010,Wix3.5 by VS2010 Votive.
thanks,
Venkat
From: Venkat Narain
To: "wix-users@lists.source
That was my first thought that it may not be possible, but then I
looked at the documentation for the LogonAsService attribute and it
says "User creation can be skipped if all that is desired is to set
this access right on the user." Likewise, for the CreateUser attribute
it says "User creation can
AFAIK, The WiXUtil User element doesn't have this functionality. I think
it can create normal accounts and normal accounts with the LogonAsService
Right. If you want to create service accounts that don't have logon
rights you'll need to write a custom action. ( I hope that I'm wrong. )
BTW
I'm running into a bit of a problem using the WixUtilExtension User
element. I'm trying to install an account which I can use for a
service I am also installing but I don't want the account to be
"created". In other words, I don't want users to be able to log in as
this user, but I want it strictly
Make sure if NEEDSREBOOT=1 getting true.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Trouble-with-ScheduleReboot-tp689116p7385293.html
Sent from the wix-users mailing list archive at Nabble.com.
-
14 matches
Mail list logo
