I need to deploy files in both C and D drives. For example File A goes to drive
C and File B goes to drive D. I know that Wix allows you to have only one root
directory. Is there any way I can accomplish this?
I know that one solution is to set C as the root directory in the Wix Xml and
deploy
I think I hit something like that. Try building the CA with AnyCPU as the
platform rather than 32/64
I have got that error when I forgot the public on the class, though
Regards
Michael
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, 11 March 2011 1
Thank you Michael,
I tried
public class CustomActions
{
private static int checkCount = 1;
[CustomAction]
public static ActionResult CheckCredentials(Session session)
{
With the same error in the log file. It seems more related to the assembly than
the sc
Hi Kevin
I think your error that it can't find the CA is in the call
private static bool CheckCredentials
Should be something like:
[CustomAction]
public static ActionResult CheckCredentials(Session session)
The class it is a member of also needs to be public.
Note yo
I hear you. Where I work there is already considerable skepticism on the
installation package and anything that goes wrong is blamed on the installation
so when the installation locks the account (because of bad credentials) there
is a call to not use any deployment and go to copy deployment bec
When I was at Continental Airlines we had an application that I had to
distribute where the service used a service account. For reasons never
determined ( aka damn service account ) something out there would periodically
lock the account and group policy would have it unlocked 10 minutes later
Hi:
On a 32-bit version of windows, your key would look like:
"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{413B7644-1F93-4890-BD40-AC540C29935B}_is1"
I don't tend to use SilentUninstallString in these situations as this stil
shows user interface--at least the cancel button if I remember
The CA is compile on a 32 bit machine and installed on a 64 bit machine. Is
that a problem? Will not WoW take care of that? It does for the other
assemblies.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
F
The same is true here running the validation with invalid credentials 3 or more
times locks the account out. So the user will not get that many tries I will
fail the installation after the first invalid entry. But this is to avoid the
situation where installing and starting the service just once
Phil and I both mentioned the potential problem. Run your code for invalid
credentials more than once. Try it about 4-12 times (as suggested by Phil). The
flow for the custom action is the following:
User enters credentials in dialog.
Dialog asks custom action to validate.
Dialog checks validati
I can check the credentials with invalid credentials and then I am able to
check the credentials using valid credentials. No lock out. Here is the code:
private static bool CheckCredentials(string userName, string password)
{
bool valid = false;
using(Princ
This is nothing to do with exceptions. I'm telling you that the act of
verifying credentials is a flavor of logon, and that a failure to "verify" may
be treated in exactly the same way as when your service tries to log on with
invalid credentials. In other words you can write a bunch of code tha
A short follow up. I had assumed this wouldn't work due to past knowledge of
the Visual Studio Express AddOn debate. However a PM from Microsoft emailed me
and it prompted me to just try it out on a VM.
I grabed the TFC install ( which uses the VS 2008 Shell in Integrated Mode )
and sure en
Hi All,
I've just rewritten my installer using WiX 3.5. However, before I
distribute the new MSI I'm dotting all the i and crossing the t's this
time! The problem is that I need to make sure the previous .exe setup
is removed before installing the new msi version.
So, i've been looking at va
I am not sure what you mean by "square one"? Are you saying that the checking
of credentials that are invalid will throw an exception that is not caught?
First I have to solve the problem that I don't think the CA is being called as
evidenced by the snippet of log I posted earlier. Unless the lo
and Kevin, are you sure that attempting to validate will not be
treated as a logon failure and put you back to square one? User account
validation schemes are often nothing more than an attempt to log on with the
supplied credentials. That might be what .ValidateCredentials does - I
do
This is where you use the property that the action set. You do not allow the
user off of the dialog until they enter credentials that work and the property
is set to the value you expect. This way it is up to the installer to exit the
install if they do not have the needed information, but you
But I want the install to fail. If it continues with the wrong credentials it
will try to start services with the wrong credentials.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Skildum, Mathew [mail
This should work if you have the entries created with default values in HKCU
where the component keypath is the registry item. This is mentioned in the
Registry Table MSDN docs where it talks about HKCU and "the installer writes
the necessary entries when there are multiple users on the same com
In cases where you checking things like credentials you want the actions to
return success so that the install does not fail. As it was said, you set a
property if the call succeeded and check if the property is set.
You use the other return values in those cases where you want the install to
So CA's always return Success. What are the other return values used for? Thank
you. For the tip.
The problem that I am having now is that it doesn't appear that the CA is
getting called. I look in the log and see the message indicated earlier in this
thread indicating that the DLL "could not b
You'll want to set a property that can be checked in a condition.
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:
Does anyone have a fix or workaround for registering COM components
that are dependent upon other type libraries being registered? Due to
the way heat is harvesting (via registry redirection) the changes, the
other components will not be available. About the only thing I can think
of is to add a
Hi all,
When our installation installs for ALLUSERS we put registry entries into
HKEY_LOCAL_MACHINE, and when the application starts on each user account we
copy the settings from there to HKEY_CURRENT_USER. This is handy because it
will work for all existing users on the machine, as well as fo
And yes, just to be clear, once I added a component under the INSTALLDIR
(not one of it's alias) the INSTALLDIR was also correctly preserved for
uninstall.
Thx,
MeCoco
On 3/10/2011 10:39 AM, MeCoco wrote:
> Thank you guys for all your help!
>
> MeCoco
>
> On 3/9/2011 4:19 PM, David Watson wrote
This error occurs when the credentials are correct. I don't get the message
that the CA is being called (the first line in the code) so I don't think the
CA is even being called.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-O
How does the custom action indicate that the credentials are incorrect?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com]
Sent: Wednesday, March 09, 2011
You patch the MSI, not the merge module, so you need to use the Component Ids
as they appear in the MSI.
Open your release MSI in something like Orca or InstEd and you can look up
the component Ids as they appear after merging. Include those in your
patch.wxs.
-Original Message-
From: Aru
Thank you guys for all your help!
MeCoco
On 3/9/2011 4:19 PM, David Watson wrote:
> 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.
>
> --
Thanks,
I'll take a look at bootstrapping.
http://msdn.microsoft.com/en-us/library/aa367553.aspx gave me the
impression that after the forecereboot, the installer would be
relaunched and I could then perform the queue set up, hence trying to
perform the MSMQ stuff before installing any files.
--
Hi All,
I am building WIX MSI that has integrated Merge Module.
Now I am creating patches for this MSI.
I know that I can specify ComponentRef's in my patch.wxs file but is there any
way to provide patch for the integrated Merge Module?
Thank You all in advance.
Regards,
AK.
DISCLAIMER
===
31 matches
Mail list logo
