Hi,
Yes, Local system have the permission (read and write) to access the network
sharing location.
I can able to create new folder, move and copy folders folders and files in
network sharing location.
Regards,
Mohamed Yasir K
--
View this message in context:
Hi,
Yes, Local system have the permission (read and write) to access the network
sharing location.
I can able to create new folder, move and copy folders folders and files in
network sharing location.
Regards,
Mohamed Yasir K
--
View this message in context:
Hi Pavan,
As already stated by Matthew Bobowski, the documentation is somewhat misleading
at this point. The condition for considering the file as modified user data is
NOT
modified date != Created date
But it is
Modified date Created date
Which means that the file has been modified after
From the documentation:
The folder must be specified in the Property attribute as the name of a
property that will have a value that resolves to the full path of the folder
before the CostInitialize action. Note that Directory ids cannot be used. For
more details, see the Remarks.
Before
Hi,
util:RemoveFolderEx - doesn't seem to work..
I'm trying to delete the installation folder and its contents upon uninstall
(the contents were created after installation by the app so they are left on
the drive after uninstall).
What am I doing wrong?
code:
Property
Hi Everyone,
I have created a setup using Wix Standard BA (Wix v3.8). Created setup
installation completed successfully if I install setup in local drive.
But it gets failed if the MSI try to ship files/folder in network shared
location. My Local machine have full rights to access the network
That is what SetProperty is for.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: ronif
Hi,
thanks for your answer,
so what is the best way to be able to reference an msiproperty i get from
burn?
MsiPackage Id=MsiPackage
SourceFile=$(var.Deployment.Package.TargetPath)
MsiProperty Name=InstallationPath
Value=[InstallationPath] /
Thanks for your help John!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-and-util-RemoveFolderEx-not-working-tp7600191p7600196.html
Sent from the wix-users mailing list archive at Nabble.com.
I was able to get it to write the URL to the config by adding the control
property to the Value of the Proerty Id: Property Id=WEB_DAV_URL
Value=WEB_DAV_URL /
The only problem with this is that WEB_DAV_URL displays in the UI Edit
field. Is there any way around this?
--
View this message in
What did the log file say?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Cockerham, Gregory [mailto:gregory.cocker...@siemens.com]
Sent: Wednesday, May 6, 2015 8:29 AM
I don't think Windows installer does any re-mapping. It just moves the
locked files to config.msi folder. There is nothing specific with installer
infact we can do it ourselves using MoveFileEx.
My take would be that whenever windows installer moves a file it should let
user know of a pending
Hi Mat,
Thank you for your email. That made a lot of sense.
--Pavan
-Original Message-
From: Reuss, Matthias [mailto:matthias.mr.re...@sivantos.com]
Sent: Tuesday, May 05, 2015 11:38 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] File not getting overwritten
The running exe and its loaded Dlls are moved, yes, but their
internals are changed so that the backing storage for their code has
changed to another location. I believe that's more than just
MoveFileEx.. And yes, you are correct, I've seen occasions when the
app in the new location will try to
OK,
problem solved,
I had one file that was locked, that failed the deletion operation,
Thanks for all your help!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-and-util-RemoveFolderEx-not-working-tp7600191p7600206.html
Sent from the
I'll provide more details. I inherited the installer codebase for a product
that has released twice (A, B) and was almost ready to release again (C).
Releases A and B have poorly written custom actions that cause them to fail
occasionally (say 5% of the time) while they are getting uninstalled as
Hi Matt,
Thank you for the email. I am a bit hesitant to use the REINSTALLMODE property,
I also noticed that in this link, has a note
Note: The Windows Installer ignores the REINSTALLMODE property during an
administrative installation.
https://msdn.microsoft.com/en-us/library/aa371182.aspx
Hello,
Thanks for getting back to me!
I tried both the safe mode option and a repair, but neither thing seems to
work.
However, I was able to find a solution, although I am a bit confused?!? If
I use Run As Adminstrator... on the Visual Studio shortcut, it works
perfectly, but otherwise it
Sorry for that,
SHOULDDELETEINSTALLATIONFOLDER = TRUE
wrapped with CDATA..
where the property is set from burn
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-and-util-RemoveFolderEx-not-working-tp7600191p7600205.html
Sent from the
Never mind, I figured it out. Another developer had inadvertently removed the
Persisted flag for the SERVICEACCOUNT variable in the Bundle file. So while
everything was set correctly for the user in the source for the MSI, the
variable not being persisted impacted the uninstalls ability to
Look at Component@/NeverOverwrite and Component@/Permanent.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original
We distribute a config file with our product (stored in
C:\ProgramData\MyCompany) that contains licensing info (entered after
installation) that doesn't change between releases.
How do I setup this file in the Product.wxs such that the file is installed
if it doesn't currently exist. If the file
Similar issue to this issue
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cant-get-util-RemoveFolderEx-to-work-on-network-drive-td7598399.html#a7598448
.
mapped network shares are defined for a specific user and typically not
accessible to a service, so msiexec probably cannot
Hi again,
you were correct about the property but for some reason the folder is still
not being delete..
Here are the relevant lines from the log:
MSI (s) (A8:90) [07:55:51:893]: Doing action: SetInstallationPathProperty
Action ended 7:55:51: ValidateProductID. Return value 1.
MSI (s) (A8:90)
What's in the inner text of Condition/Condition? Note that, unless the
Component is marked Transitive, that Condition gets evaluated only once. It
looks like the Component was not selected, and that would point to the
Component-Condition.
--
John Merryweather Cooper
Senior Software Engineer
Hi,
I am asked to package a piece of software which consists an executable
and a DLL file. However suppose if I want the executable to be run
automatically at boot time, how can I specify this?
Actually the program opens a web socket. How can I run it at boot
time as an administrator without
You'll need to escape it. It's not showing on this end.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
The inner text is:
Component Id=InstalladtionPathCleanup
Directory=InstallationPath
Guid=A4E116FE-B9C9-499C-BBC5-27BC88B21945
Condition
/Condition
CreateFolder Directory=InstallationPath /
util:RemoveFolderEx
I am creating a user during my install and adding that user to the
Administrators group:
Component Id=cmpId Guid=guid Win64=yes KeyPath=yes
CreateFolder/
util:User Id=systemAdmin CreateUser=yes
RemoveOnUninstall=yes FailIfExists=no Name=[SERVICEACCOUNT]
29 matches
Mail list logo
