Hi Blair,
I tried the 2nd approach and it worked. The specific script and command I used
are shown below.
Thanks a lot,
Miaohsi
"%HeatDir%\heat.exe" dir "%SrcRootDir%\de" -cg IMC_DE -ag -scom -sreg -sfrag
-dr IntelaTrac -var wix.IntelaTracPath.de -out "%CleintPrjDir%\Files\IMC_DE.wx
I'm pretty sure I've seen this on stackoverflow and possibly also in this mail
list. In general, it is an XSL/XSLT general problem of using a modified
"identity transform" to remove elements in the transform based on an XPath (you
can add multiple exclusions if you need to). Variations on this i
Just tested that and no change, unfortunately. I'll also note that when the
services were correctly uninstalling in the past, I would have the Services
window open, and I could refresh it to see that the services were completely
removed.
But in debugging, we stumbled upon the reason for this Di
When this gets solved, I will leave behind detailed info on how to make it work
in a final post. In addition there will be the "struggle" along the way in
this thread. Hopefully these things should clear up any future confusion.
From: Hoover, Jacob [via Windows Installer XML (WiX) toolset]
[m
Good question, I will check.
From: Hoover, Jacob [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7587007...@n2.nabble.com]
Sent: Friday, June 28, 2013 2:43 PM
To: Mark Van Dyke
Subject: Re: Burn - Localization Identifiers Duplicated
I have not personally localized a bundle. Th
I have not personally localized a bundle. The hints and pointers I am giving
you are based off of the current Wix codebase. Wix has had several generations
of developers and the documentation is less than perfect. (It's open source,
so anyone is welcome to contribute more documentation / how
I have tried these suggestions too and I have, again, tried variations on them
- all to no avail. Here is the current iteration:
I changed all my localization folders to be lowercase (en-us instead of en-US)
in case something in WiX was case-sens
OK, the file version and Assembly version are all OK.
Thanks
Ruth
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: Friday, June 28, 2013 1:26 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] timestamp of dlls is not right in w
Do you still have the computer management console open when doing the uninstall
(but after stopping the service)? I seem to remember bugs in the snap in that
either leaked handles or maintained an exclusive lock on the SCM that would
exhibit this behavior.
-Original Message-
From: Alain
The MST doesn't have to be embedded, it's just "easier" to do it that way. You
could just as easily have them external, and instead of
Value=":[TransformFileName].mst" use Value="[TransformFileName].mst". Then you
would need a http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multip
Thanks Phil!
Let me explain more clearly:
After installation, in C:\Windows\Microsoft.NET\assembly\GAC_MSIL, the
installer creates folders for each dll.
For example:
For one of our dll (SPCLClient.dll)
The folder structure is: ...\ GAC_MSIL \SPCLClient\
v4.0_1.0.0.0__162e49f266e4cfc2\ SPCLClient
I'll open by saying that I don't think this is why the services are being
disabled, because I'm not even using this part of our client yet. All I'm doing
right now to test this is installing our software, manually (in Services)
stopping our services (to "simulate" what our software would do befo
Thanks for the response...
No we are not going to be showing the MSI in UI. What is in the language
.mst files are the application shortcuts. The names of the shortcuts are
translated and therefore if say you are on a french machine then we want the
shortcuts to be in French...
We have not looked
I would concur with Blair. I also seem to remember the reasoning behind this
was older supported operating systems (XP) didn't have an API to get the
"friendly" names. (Ex: GetUserDefaultLangID vs GetUserDefaultLocaleName)
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Se
As I understand it, in the Name attribute you need to use the LCID instead of
the culture name.
For instance:
where 1028 is the LCID for the culture known as zh-tw.
Blair
> Date: Fri, 28 Jun 2013 11:30:52 -0700
> From: ma...@costar.ca
> To: wix-users@lists.sourceforge.net
> Subject: Re: [Wi
...the OP has folders in the GAC? That seems rather strange to me. The GAC
and the way Windows finds files there preclude the use of user folders.
Phil
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Friday, June 28, 2013 11:52 AM
To: General discussion for Windows I
Any process that wants to do something with a service (such as stop it) has
a Windows handle open to it. In managed code you'd use a ServiceController
class, and the Dispose() method in that class is explicitly there to release
unmanaged resources like that service handle. By "managed" I mean Micro
Microsoft. Windows Installer, Fusion, and the GAC are theirs.
> From: ruth...@intergraph.com
> To: wix-users@lists.sourceforge.net;
> imceamailto-osito+40live+2e...@ingrnet.com
> Date: Fri, 28 Jun 2013 14:00:07 +
> Subject: Re: [WiX-users] Wix uninstall does not remove folders in GAC and
>
OK, I have tried some different variations on Blair and Jacob's suggestions.
None have worked and there has been varying degrees of success. The most
successful correctly displayed the default Preqba.wxl entries that I have
defined (which are in English but my regional settings are fr-CA) but
Windows Installer sets Creation Date to be the same as Modify Date for files
it installs. It's not a WiX thing, it's Windows. With binary files the
expectation is that File Version is what identifies it, not a date. It's a
bit more complicated in the GAC because assembly identity is more than just
Why not localize the Burn bundle? Can you not utilize one MSI with component
conditions based on language (assuming you have language specific files to
deploy)? Are you trying to show the MSI's UI?
Depending on what your MST changes, you might be able to utilize
SystemLanguageID - gets the la
Can you clarify what you mean by "If any process has a handle open to a
service"? Isn't it the service that runs/spawns/opens a handle to a process,
and not the other way around? And isn't it the service that tries to stop the
process when the service is told to stop?
Our code is all in Java (s
I've mentioned this before, but I don't recall if it was in connection with
this thread...
If any process has a handle open to a service, then Windows can't delete it
so it gets marked disabled. In code this tends to be code that doesn't close
handles , whether explicitly in C++ or in managed code
I am creating my first bootstrapper .exe that installs some prerequisites
.exe and then triggers my WiX .msi installer.
This all works ok, only using basic Burn UI, but now I want to look at
passing in language transform .mst to the product .msi and therefore I would
like to know how this is done?
Just to wrap up my initial question - I went eventually with the Visual
Studio Boostsrapper and followed this blog post:
http://blogs.msdn.com/b/astebner/archive/2008/11/21/9132456.aspx to achieve
what I wanted.
It gave me exactly what I needed.
My msbuild file looks like that (file name is boosts
Thank you for replay.
But i would like to only uninstall it (without install newer version) - by
Plan(LaunchAction.Uninstall);
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Friday, June 28, 2013 3:39 PM
To: 'General discussion for Windows Installer XML toolset.'
That solved it. Thanks Neil :)
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 28 June 2013 15:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] FAO Neil Sleightholm
Somebody had this once before and it was due to windows 7
Thank you, Blair. I'll try the approaches and let you know the result. By the
way, while googling on the solution to the issue, I found some people proposed
the use -t option to use transform to exclude files from the output wxs file,
which is my next challenge. However, I did not find documents
What would be really handy is a ba/ux with a feature tree selection driving
multiple msi packages. This would need to be in addition to WixStdBA, but
"getting it right" and doing it in a reusable way isn't a trivial task.
Handling upgrades would be especially tricky as a bundle can't currently
Microsoft Office 2007 has a single entry in ARP that can be used to
modify/remove the installed products. I wonder if they are using Burn to do
that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-separate-entries-in-Add-Remove-for-each-M
Are you installing some sort of suite of different products? Maybe the
Visible flag on the MsiPackage element will get you closer to what you want.
Or there might be a way to build a custom BA that would present a screen to
remove particular products.
--
View this message in context:
http://wi
Somebody had this once before and it was due to windows 7 blocking the
file, try right clicking and looking at the file properties. If you have
further issues please post a question on the codeplex discussion and I'Ll
answer it there.
Neil
>I have been following your blog and I am now trying to
Yes, the cmd.exe is from a .bat file the service executes. Making it read-only
did give the uninstaller pause as it took longer before finally deciding to
still request a restart.
One of my team members pointed something out that I should have realised: Since
this problem is mainly causing prob
I have been following your blog and I am now trying to use your extended
bootstrapper. I have an issue however where it will not allow me to add a
reference to your WixBalExtensionExt.dll, it gives an error saying it is not
a valid WiX source file.
Would you know what I am doing wrong?
Than
Thanks Blair!
The empty folders are inside GAC, so I have no way to delete them. Do you know
any way to report this bug so that I can keep a record in my side.
I do have logic of RemoveFolder to remove the empty folders under product's
directory tree.
Ruth
-Original Message-
From: Blai
Thanks for replying.
Both Creation time and Modification time of the dlls show the installation date
instead of package/build time.
Ruth
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Thursday, June 27, 2013 6:42 PM
To: General discussion for Windows Installer XML to
So long as the Bundles' UpgradeCode is identical, I would think a MajorUpgrade
would uninstall the older version and install the new one.
However, something beyond my installer knowledge may be going on, since I don't
know what may be causing this line:
[23D0:26C4][2013-06-28T10:38:09]w354: Una
As I imagine it, checks for prerequisites would be performed silently. If all
pre-req's are already installed, it would launch right into the MSI(s). If any
pre-req's need to be installed, they would be, while an informational message
is displayed, perhaps with a progress bar. It would be okay
Hello,
Is there any way how can i uninstall older version of application from
different bundle (newer installer)?
It works only with the same build which installed it. When i try it, i get
followig "error" :
T10:38:03]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0),
path: C:\
Rob,
Thanks, I need about the MsiPakage properties. Here the MsiPackage in the
bundle.wxs.
Both SourceFile and DownloadUrl has updated in MsiPackage, in this case
which one will going to install?
Is this take msi from DownloadUrl?
Thanks,
Kannan
--
View this m
I might rise to the challenge but I would like to understand how this
would work. Do you see it displaying any UI or just silently installing
pre-reqs? That sounds a little bit anti-social just installing something
without warning.
Neil
>There are several people on this list who might be convinc
41 matches
Mail list logo
