erencing any assemblies that are not part of the .net
BCL's?
>>
>> On Tue, Jun 23, 2009 at 2:25 PM, Tina Basinger
wrote:
>>
>>> It is a managed custom action, that I've run through the MakeSfxCA
tool.
>>> .NET is installed on the machine.
>>>
If the CA is managed it requires .net
If it's unmanaged it requires the VC runtime unless you compile it with
/MT to embed the runtime in the dll.
(http://msdn.microsoft.com/en-us/library/2kzt1wy3(VS.80).aspx)
Installing VS.NET would install both of these... It could be some other
dependency as we
You have to use a bootstrapper with an embedded manifest that launches
the MSI to do that. I think it's considered best practice to let the
dialog come before the file copy as it does by default.
-Brooke
-Original Message-
From: sandun css [mailto:sandun...@gmail.com]
Sent: Monday, June
I did everything in raw xml in visual studio. I edited a couple of the
ui elements in SharpDevelop as it has a wix Dialog editor which makes
visualization of the UI easier than having to compile/run. I found that
manually doing most of it helped me understand the underlying
relationship between eve
I ran into this same issue. If you need any Immediate action to run with
admin rights when UAC is enabled you have to launch the setup as an
administrator. Also if you set Impersonate to 'yes' for a deferred
action unless you start the install with elevated rights the
impersonated deferred action w
g database logon credentials to the service account (we have
to support sql auth credentials from the service to our database).
Brooke Philpott, Senior Technical Lead, SQL Sentry, Inc.
P: 704.895.6241 x228 | F: 704.895.8771 | E: bphilp...@sqlsentry.net | B:
brooke.blogs.sqlsentry.net
-Origin
When I do a fresh install I'm using a bootstrapper to launch the msi
with admin rights so I can perform a LogonUser call in order to validate
the account used during the execution phase for the service. I want to
do that validation up front so I don't get an error during the execution
phase which w
I'm currently using setupbld to generate a setup wrapper. However when I
sign the output using signtool it corrupts the executable. Trying to run
the resultant exe post signing yields an error:
Activation context generation failed for "...\badsetup.exe".Error in
manifest or policy file "...\badset
8 matches
Mail list logo
