It is worth noting that the MSI web setups generated by Visual Studio (I am
using 2008) need "IIS6 management compatibilty" to be installed first on the
target system for the MS generated MSI setups to work, if you are installing
on an IIS7 system. This is one of the great things about Wix is that
Hi Sam
Have a look at these:
http://stackoverflow.com/questions/471424/wix-tricks-and-best-practices
http://www.brianpeek.com/blog/archive/2007/11/13/x64-development-with-net.aspx
http://stackoverflow.com/questions/516730/visual-studio-any-cpu-target
There are some good approaches that I've used
I think you need to use a component group:
heat ... -cg WebSiteFiles
This wraps all your components up into a single component grouping that you
can then reference easily in your feature:
Richard
2009/8/6 bonn deng
> Hi all, I am now using heat.exe to generate the .wxs file of on
What about using the ComputerName property?
e.g.
or I use this for a deferred action, you could easily adapt this for your
needs with the [ComputerName] property:
Cheers
Richard
2009/8/6 Jiang, Chunyan (GE Healthcare)
> Hi Wix-user,
>
> I want to define one Custom Action like this:
>
Hey everyone
My installed IIS application locks a log file that doesn't release until the
application/and or the pool has been stopped. I'm finding that during
uninstall that I get prompted for a reboot because of this I suspect - IIS
website still running when it tries to remove all the files.
5 matches
Mail list logo