Hi Phil,
I can control error from custom action like that:
When error's occured, I use return value is suspend instead to failure.
Installer will be suspend and no dialog display.
Thanks,
On 10 April 2012 00:49, Wilson, Phil phil.wil...@invensys.com wrote:
Do you have any more details of the
Dear all,
I'm using setup.exe and setupbld.exe from (%WixProramFolder%\bin\)to make a
bootstrapper for my installer. Everything is ok except:
I want to get current directory of setup.exe but:
1. When I use property CURRENTDIRECTORY, I will get wrong value if I run
command line in cmd.exe:
With very careful coding, you should be able create a minor upgrade from an
InstallShield based MSI. It's all just MSI in the end.
On Fri, May 11, 2012 at 12:34 AM, Christoph Goetz
christoph.go...@giepa.dewrote:
Sorry
Hi,
we use Install Shield but we want to change to WIX.
If we want to
Yeah, that's it.
On Thu, May 10, 2012 at 6:21 AM, Lars Augensen
lars.augen...@confirmit.comwrote:
This turned out to be the best solution:
iis:WebSite Id=WebSiteID Description=A_Web_Site SiteId=123456789
AutoStart=no StartOnInstall=no Directory=DIR
iis:WebAddress Id=Web1 Port=80/
Yeah, pain isn't it. Visual Studio holds lock on MSBuild tasks as well.
On Fri, May 11, 2012 at 1:43 AM, Morten Lemvigh
morten.lemv...@novasoftware.se wrote:
When building a setup project using Votive in Visual Studio, a handle is
kept on any extension dlls even after the build has completed.
Yes I ran both,
C:\Windows\system32\\bcdedit.exe /set testsigning on - worked on a command
line that was run as administrator
C:\Windows\system32\\bcdedit.exe /set testsigning on - this did not
work, my mistake
--
View this message in context:
On 13-05-2012 23:42, Rob Mensching wrote:
Yeah, pain isn't it. Visual Studio holds lock on MSBuild tasks as well.
!Truly! Have you any experience executing the extension in a new
separate AppDomain and thereby being able to unload it again? I started
out but ended up in a dark alley of missing
7 matches
Mail list logo
