Hi
On my dev box (win7 64bit), I'm finding that when I uninstall my web
application, everything gets properly removed EXCEPT the AppPool.
I found a related thread:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-Application-pools-in-IIS-on-Windows-7-2008-td5438654.htm
Dear Team
I am evaluating WiX, NSIS & Inno Setup, VS2008 Setup for my deployment
scenario.
I have the following scenario for deployment -
1. Bootstrapper for Pre-Requisites
Available in VS 2008
2. Custom UI for Customer Data
Available in VS 2008(Restricted UI Set)
3. On
Thanks, Yan!
I looked for the bug but couldn't find it so ensured one was logged.
(https://sourceforge.net/tracker/?func=detail&aid=3185104&group_id=105970&atid=642714)
John
Wintellect
http://www.wintellect.com
+1-877-968-5528
-Original Message-
From: Rob Mensching [mailto:r...@robme
Hey Palbinder,
Which version of heat.exe are you using? As long as you aren't using -suid
you should be ok.
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove
On Thu, Feb 17, 2011 at 2:10 AM, wrote:
> Hi Palbinder, (group),
>
> thanks for your response.
For the "uninstall handler" (meaning the application which uninstalls
the MSIs) I'd recommend to use the UpgradeCode to query the
ProductCode to get more flexibility. Following DTF code sample
illustrates that and uninstalls here the Microsoft SQL Server Compact
3.5 (or other versions sharing the U
Also i read that max size of msi is 2Gb, so i can not embed all files
into single msi.
The Cabinet format has a max limit of 2 GB. That doesn't mean you can't
use multiple Media elements to compress your files into multiple cabs &
embed them into your MSI if you wish. I wouldn't recommend embeddin
Did you consider administrative installation
(http://msdn.microsoft.com/en-us/library/aa367541%28v=vs.85%29.aspx) ?
Unfortunately I'm not well informed about this technique but it might
be interesting for the described scenario.
Regards
Tobias
2011/2/17 Rob Mensching :
> 1. Yes, you can specify
1. Yes, you can specify files in your MSI to not be compressed. You can also
specify none of your files in your MSI to be compressed
Package/@Compressed="no" (the default, I believe).
2. Yes, Media/@EmbedCab="no" (the default, I believe) creates non-embedded
cabinets.
3. Yes, it is possible to ma
I believe a bug is open on this and possibly already fixed in WiX v3.6.
On Thu, Feb 17, 2011 at 3:12 AM, Christopher Painter <
chr...@deploymentengineering.com> wrote:
> Ah, good to know. Certainly sounds like a bug to me. I wonder how that
> works
> in a merge module consumed by an installer.
Hi Tobias,
Thanks for the pointers. I've been looking at the setupbld.exe but it seems
to be only partially implemented
-bitmap and -privilege both do nothing and I'd also like an -icon to set the
icon of the exe too.
I was taking a look to see if I could build these myself
-Original Mes
1 - What I would like is for the extension installers to refuse being
installed if the main application isn't installed.
This is easily supported using LaunchConditions in an MSI. Simply use
something like a RegistrySearch to populate a property with something
your main product installs then use t
Hmm, something is wrong in your MSI if it needs to be launched elevated.
Visual Studio 2010 shipped last year so I don't think their bootstrapper
project would be a work in progress. It either works or they shipped with a
bug.
On Thu, Feb 17, 2011 at 2:55 AM, Michael Tissington <
michael_tissing
Hi,
Have a look at the wix included tool setupbld.exe. Think this should
be able to create a setup.exe wrapper which runs as admin. But afaik
no possibility to generate a log file.
Other options are full bootstrappers like DotNetInstaller of Burn
which is under development. Visual Studio 2010 Boo
No one?
/Thomas Due
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: 11. februar 2011 09:00
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Best practice for making dependent installers
Hi,
I am maintaining the installer for our main product. This product
Hi,
I need to prepare msi installer, so that it could be installed via
Active Directory on multiple computers in silent mode.
Total size of files, i must redistribute is about 100Gb, so it would be
significant optimization, not to pack into cab (or at least pack without
compression) ant not to
Ah, good to know. Certainly sounds like a bug to me. I wonder how that works
in a merge module consumed by an installer. I'll have to try it.
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-
That seems like a something to me. I'd say what but I don't feel like having
my
spelling challenged.
Kind of like how InstallShield couldn't create a web site that didn't also have
a Virtual Directory because the custom tables had a join between Component and
Virtual Directory.I'm not su
I've looked thru lots of google results trying to find out how to build a
setup.exe from a single wix generated msi file.
Visual Studio 2010 has a bootstrapper project but that looks like a work in
process, am I right?
Basically all I need my setup to do is to launch the msi and create a log
f
Would creating a pure Wix patch from administrative installations work for
you ? It's what we do here.
This gives you an idea of the process.
http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-didn
t-build-with-wix-using-wix-.aspx
-Original Message-
From: Liam Flanaga
Hello All,
Is there any way to view a wixmst file created via torch in the following
manner:
torch -xi -xo RTM.wixpdb QFE.wixpdb -out diff.wixmst
I was under the impression that the output file should be a xml; however I
appear to get a lot of excess at the top of the file which appears
Hi,
Am 17.02.2011 02:07, schrieb Bob Arnson:
> On 16-Feb-11 17:13, Lukas Haase wrote:
>> However, what happens when program with same UpgradeCode is first
>> installed globally as administrator and the next version installed as
>> non-admin user?
>
> MSI doesn't support a per-machine package upgra
Hi Palbinder, (group),
thanks for your response.
As per the link you said, an ID of "1234" is *not* acceptable ("every
identifier must begin with either a letter or an underscore"), which is why I
think heat does some magic to avoid that ID for a directory called "1234".
It seems that in one c
Hello WiX Community,
Well, actually the subject tells it all. I'm aware of this limitation, and
I've been successfully using the CA working with temporary data.
Now I'd like to know the reasoning behind this. Is it a technical
limitation? Why we can't "temporary" change the persistent data, just f
23 matches
Mail list logo