Thanks for clarifying. We were able to suppress UAC by using
ApplicationRequiresElevation="true". So, it's certainly doable. I'm trying
to find out how to do it in 3.6 as we no longer use the GenerateBootstrapper
task.
--
View this message in context:
http://windows-installer-xml-wix-toolset.68
We use the VS 2010 plug-in, which uses candle and light exes. We don't use
burn.exe per se. So, I'm not sure how I can add the /quiet switch.
Also, for the other question, are you saying that there's no way to work
around the UAC warnings with Burn?
Thanks
Erkan
--
View
wn custom BA to do that. Did
anyone do that yet?
Also, with 3.5, we had the following msbuild task to generate the bootstrapper:
http://www.xyz.com"; />
ApplicationRequiresElevation="true" prevents the UAC warnings.
How can we do the same w
I'm not sure what you mean by that. " Merge Modules append the Module/@Id to
all identifiers."
Which identifiers? How is that breaking the escape characters? Could you please
elaborate?
Thanks in advance
Erkan Celme
Phone: 312-927-5180
-Original Message-
From: Rob Mens
yone have any idea why it doesn't work
the same way in a merge module? Any ideas on how to work around this?
Thanks in advance.
Erkan
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Kno
5 matches
Mail list logo