Hi, Rob! I'm afraid that nothing about old.msi.
My_Designer_20130221204804(InstallNewBundle-MinorUpdate).log
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7583866/My_Designer_20130221204804.log
My_Designer_20130221204828(quietUninstallOldBundle).log
Hi all,
I am trying to set up a DirectorySearch element to set a property.
My directorySearch currently looks like the following:
Property Id=JAWS14USERENUSCRIPTINSTALLPATH Secure=yes
DirectorySearch Id=UserAppData Path=[AppDataFolder]
DirectorySearch Id=FreedomScientificUser
Hi, thanks for answering.
I already have an API in my service to enable a modem (needed to set up a
phonebook entry at install time), so I figured I'd reuse it.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's
Sorry, but i am not sure what that would entail. Can you elaborate?
The PowerShell scripts are required by the chocolatey infrastructure.
Gary
Sent from my Windows Phone
From: Gabriel Ivanesmailto:g...@fastmail.net
Sent: 22/02/2013 09:33
To: General
Why not just split that code into it's own class and then use it directly in
the custom action? It seems like a lot of infrastructure (i.e. a lot of
things to break) for a CA to make an IPC call to a running service.
From: keith.doug...@statcan.gc.ca
I suppose I could use reflection in both cases, but that's ugly ... The idea
was just to use the same mechanism used by our other programs (which are
userland but have to enable/disable certain devices - hence the service). Since
the installation is already privileged (or will be, I guess)
This is an interesting circumstance. Chocolatey is a new way of deploying
software packages, sort of like apt-get on Linux. Ordinarily, upgrading
software that was previously installed via an MSI is easy. You just author a
major upgrade into the next MSI or you create a patch. I'm not familiar
Hello Nick,
Thanks for all the info!!
Yes, normally chocolatey goes off and downloads the msi/exe from the
internet, and then installs it (with whatever flags are required to
silence the install). A typical install PowerShell script looks like
this:
That sounds right to me. Use a MajorUpgrade element to handle the upgrade.
That will replace the obsolete version and replace it with the new one.
You'll just need to manually change the Product's Id (and Product version)
in updated versions of the MSI.
--
View this message in context:
I have some files which need to be eliminated from .WXS based on given Input
of environment like dev,prod which will be passed as a property to Heat.exe.
Based on that I need to filter out or remove some files from Fragment.WXS
after harvesting through XSLT transformation. For Example if the xslt
Perfect! I think I can work with this then.
Our build script already handles the creation of the version number, so I
should be able to generate a new GUID for the ProductCode, and then use this
same GUID in the uninstall script.
Let me try this out, and see how I get on.
Thanks!
Gary
--
So is there a different install/uninstall set of URLs for each MSI version?
Just curious.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583881.html
Sent from the wix-users mailing list archive at Nabble.com.
I have a custom managed bootstrapper and I want to get a parameter from the
msi package that are installed in the bundle. So, when the msi has been
installed I want to get the installation directory out to the bootstrapper.
How can this be done in the best way? I read about storing values in the
Hello,
From what I have seen, no, typically the download url's remain the same
across different versions of the application.
I personally maintain the chocolatey package for an application called
calibre (and have done for almost the last year) and the download url has
never changed, and there
Are you selecting this location via the BA or the MSI? The best way to do this
would be via the bundle, and pass it into the MSI as a property. That way you
can tell burn to remember the value of the variable for you.
Variable Name=Foo Value=[ProgramFilesFolder]\Bar Persisted=yes/
MsiPackage
Hi peter,
I have got the xslt template which works partially ie;the requirement was
to eliminate dev,prod ,uat files from harvest file through XSLT template, if
package is to be deployed in test env similarly for other environments
also.But I am not sure is their any command of heat where we
Hi,
how can I define a File/@Source attribute to be relative to the
wix-library Project folder, where I am currently in?
If I use:
File Id=f1 Source=.\bla/
then . refers to the root of the refering Windows Installer Package
Project (currently compiling), and for this reason can not be used!
I
I could do that actually. Thanks for the tip!
/Kristian
2013/2/22 Hoover, Jacob jacob.hoo...@greenheck.com
Are you selecting this location via the BA or the MSI? The best way to do
this would be via the bundle, and pass it into the MSI as a property. That
way you can tell burn to remember
Nothing built in to do that today.
On Fri, Feb 22, 2013 at 11:20 AM, Jerome Rougnon-Glasson
jerom...@gmx.netwrote:
Hi,
how can I define a File/@Source attribute to be relative to the
wix-library Project folder, where I am currently in?
If I use:
File Id=f1 Source=.\bla/
then . refers
Any one?
Am 14.12.2012 10:24, schrieb Michael Scheepers:
Hi there,
I do have a problem setting a property by the Publish element filled
with a text from a locale file, cause it contains a new line.
Is there a way to escape the \r\n in the locale file so I can use it in
the Publish element?
On 21-Feb-13 09:13, Gabriel Ivanes wrote:
Anyone knows why does the bit FirstSequence automatically set Rollback's
bit ?
The same with OncePerProcess and Commit.
Because they're the same bits. msidbCustomActionTypeFirstSequence and
msidbCustomActionTypeOncePerProcess are only valid for
21 matches
Mail list logo
