Hi Michael,
Thanks for your answer.
Is the following code not enough to preserve the INSTALLDIR directory?
Fragment
DirectoryRef Id=INSTALLDIR
Directory Id=MyApp.Binaries /
/DirectoryRef
/Fragment
Fragment
Component Id=MyApp.Binaries.app.config Directory=MyApp.Binaries
Guid=MY-GUID
File
Hi,
I've recently done something similar. I look at the registry to see if
MSMQ is installed and store the result in a property:
Property Id='MSMQAVAILABLE'
RegistrySearch Id=MSMQIsInstalled
Root=HKLM
I have installed the Windows Server 2008 R2 with Hyper-V Manager and I
am now installing the guests. Much easier this way although I got the
standalone Hyper-V server going but time is important right now.
I guess I can just export the VM's for safe keeping and whenever I need
a clean system I
You can do it by publishing property changes depending on the state of the
selection tree in SelectionTree control and then later using those
properties.
and then handling disable for the next button
DisableButton = 1
DisableButton
My previous post seems to be mangled in the editor so without giving the
markup I will just suggest the way to do it.
You can do it by publishing property changes depending on the state of the
selection tree in SelectionTree control and then later using those
properties.
This was suggested by
I consistently get an account lockout when I install and start a service with
the wrong credentials. Everything works fine when the proper credentials are
supplied. I know it is probably an FAQ but I am just beginning. What facilities
are available for checking the credentials and rolling back
Not yet.
On Tue, Mar 8, 2011 at 7:45 AM, Michael Tissington
michael_tissing...@ciqual.com wrote:
OK, I think I'm going to stick with 3.1
What is the state of Burn ... is it possible to modify the UI and show the
msi UI ?
Thanks.
-Original Message-
From: Rob Mensching
That doesn't look like it creates a component whose Directory is
INSTALLDIR. It may put the component's file in the same directory, but
since custom actions could override this, it doesn't count. What you
need is the Directory_ column of the Component table to say INSTALLDIR
instead of
Hi Michael,
Thanks again for the explanation.
Could you also tell me please what are the following lines of code
actually do?:
DirectoryRef Id=INSTALLDIR
Directory Id=MyApp.Binaries /
/DirectoryRef
Thanks!
MeCoco
On 3/9/2011 3:08 PM, Michael Urman wrote:
That doesn't look like it creates a
If you have a directory element with no @Name it just makes the @Id an alias
of the containing element.
So your code makes any files targeted to MyApp.Binaries go in the same
location as INSTALLDIR.
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 09 March 2011
I've been doing a lot of work with collaboration and TFS lately and I've been
wondering something. Team Foundation Server Client ( aka TFC aka Team
Explorer
) has an installer that gives you a stock Visual Studio IDE / Shell and
installs
the Team Explorer AddIn. This allows non-developer
Hi,
I'm getting a bit frustrated with constantly rebooting to try and get
this working.
If MSMQ is installed the queue gets created. If MSMQ isn't installed,
it gets installed and throws the following message before forcing the
reboot:
The installer has encountered an unexpected error
Put a launch condition in that cancels your installation if msmq is not
installed.
If you really need to install msmq for your user use a bootstrapper that
installs it before your msi is called.
-Original Message-
From: Matthew Slane [mailto:matthew.sl...@thetrainline.com]
Sent: 09
I have a very simple C# Custom Action that is supposed to verify credentials:
using Microsoft.Deployment.WindowsInstaller;
namespace BuySeasons.BsiServices.Install
{
public class CustomActions
{
[CustomAction]
public static ActionResult CheckCredentials(Session session)
If I had to guess you calling this CA as a ControlEvent off a Dialog / Control
in your UI sequence. Am I correct? If so, it's a known issue that Msi lacks
the ability to process messages in this scenario. The workaround is to set a
dummy property to see a PROPERTY CHANGED message in the log
There are no builtin facilities in Windows Installer nor WiX for checking
credentials. You'll need to write a custom action to perform this type of check
but beware that this check will likely count against the lockout count if the
credentials are incorrect. In other words, if you use the
It is locking out the account. It is rolling back so nothing is installed but
the account is locked out when invalid credentials are supplied. I don't know
how to go about debugging this issue.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
I think I have solved this problem. The CA was scheduled in the
InstallExecuteSequence and was marked as 'deferred' so I created the following
'Custom Data'.
CustomAction Id=SetProperty Property=CA_CheckCredentials
Value=[SERVICEUSER],[SERVICEPASSWORD] /
CustomAction
ICE63 - http://msdn.microsoft.com/en-us/library/aa369008.aspx
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From:
I read that. Which of the four rules is this violating?
I made the warning go away by making the C# CA 'immediate' thus I don't have to
have another custom action to remember the property. So I have
CustomAction Id=CA_CheckCredentials
Return=check
You shouldn't return failure if the credentials are incorrect, if you do so
you will get this error.
been there, done that...
On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote:
I read that. Which of the four rules is this violating?
I made the warning go away by making the C#
21 matches
Mail list logo
