Hi,
When I add a reference to WixUtilExtension in my WiX project, this is what
gets added to the .wixproj:
$(WixExtDir)\WixUtilExtension.dll
WixUtilExtension
When my colleague does this, he sometimes gets the above, but usually gets
this:
..\..\..\..\..\..\..\..\.
When:
1) A cmd prompt is opened (in this case using the VS2010 CMD prompt)
2) A batch file which has setlocal also has a "set
projectPath=some_path_to_a_folder" (case of the variable name does not
matter)
3) And at some point in the same batch file or a different batch file (also
using setlocal) bu
Apologies in advance for the noob question - I HAVE tried various options but
I'm stuck!
I have a C# project (VS 2010) that creates a .NET DLL containing (amongst other
things) a number of performance counters all in a single category. I'd like to
harvest them using heat.exe rather than having
I think you have to register the performance counters using the .NET tools
and then harvest them.
Neil
>Apologies in advance for the noob question - I HAVE tried various options
>but I'm stuck!
>
>I have a C# project (VS 2010) that creates a .NET DLL containing (amongst
>other things) a number o
Yes, the MSI package has the following:
When this package is launched as part of the bundle chain the log indicates
that ALLUSERS is 1.
This package has been installing with the feature advertized, but without
complaining about this registry value for some time. However I recently
refactored s
Thanks Rob...
It actually turned out to be the first build I did from TeamCity did not
link in the merge module as it did not have access to it at the time. So the
wixlib that went into the parent just did not have the merge module to
install.
So I re-verified with the latest build and it correct
It worked...
Quoting Carter Young :
> I'm aiming for RuntimeVersion <=13.0.8, I'll give this a try tomorrow...
>
> Carter
>
> On Thursday, April 10, 2014 04:49:47 PM Phill Hogland wrote:
>> In the prior post I meant to have the entity display:
>> InstallCondition="RuntimeVersion <=vx.x.x.x"
>>
Hi,
I would like to know, what's the best Way for Updating PeogressBar and
StatusText From c# Custom Action.
Sincerly
Chris
Wichtiger Hinweis: Diese E-Mail und etwa angehängte Dateien können vertrauliche
Informationen enthalten und sind ausschließlich für den/die Adressaten
bestimmt. Sollten
Thanks Rob. Is there a work around to achieve this?
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Thursday, April 10, 2014 11:34 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Adding msi/exe packages outside the burn chain
No. Burn pr
Is there a way to bypass the security features of the Burn engine designed to
prevent evil people from slipping malware into your Bundle? I certainly hope
not. If you find such a bug, please do let us know.
___
FireGiant | Dedicated
Got it. Thank you Rob.
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Friday, April 11, 2014 10:38 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Adding msi/exe packages outside the burn chain
Is there a way to bypass the security feat
The general methodology is here:
http://msdn.microsoft.com/en-us/library/aa367525(v=vs.85).aspx
That covers the APIs which probably have C# mappings in DTF (if that's
what you're using)
The status text comes from the ActionText MSI table, WiX ProgressText.
The format is templated and many setups
When you say it's advertised, I'm not sure whether you're referring to
other users on the machine, and if some of the scenarios are about an
administrator doing a repair but a limited user can't use the
advertised feature correctly.
If it's registry data intended for different users it typically g
...ooops MsiLogging, which seems NOT to like * so spell out the options..
---
Phil Wilson
On Fri, Apr 11, 2014 at 12:01 PM, Phil Wilson wrote:
> When you say it's advertised, I'm not sure whether you're referring to
> other users on the machine, and if some of the scenarios are
Note: there have been discussions about adding a feature called "modifiable
chain" to Burn. However, the security implications are massively challenging
and backwards compatibility would be ratcheted up. At this point, is far more
straight forward and secure to distribute an updated bundle. Sinc
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
Hi all,
How does one handle the situation where the Util:XmlFile custom action logs
sensitive information to the log file?
Eg:
MSI (s) (F8:8C) [11:43:03:072]: Executing op:
ActionStart(Name=ExecXmlFile,,)
MSI (s) (F8:8C) [11:43:03:074]: Executing op:
CustomActionSchedule(Action=ExecXmlFile,Action
I don't want to violate the security. The applications in the bundle were
installed on the first install in a per-machine install. Burn was elevated
at the UAC prompt. There are many other keys which are part of this app
which are also written under HKLM. (I am not intending to do a per-user
ins
18 matches
Mail list logo
