How to determine the location of install files

[JDS]

I am using a setup project and Windows Installer to deploy my
application and have some additional code in custom actions. In this
code I need to refer to one of the install files but I cannot find how
to determine the path. For example, if the install CD is in the d:
drive and the user runs d:\setup.exe I want to know that it has been
run from d: (rather than e: or any other location) so that I can build
up the path to one of the folders on the CD.

I do not want to copy the file as part of the installation because it
is large and not required once installation is complete.

Can anyone help?

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

"JDS" wrote:

I am using a setup project and Windows Installer to deploy my
application and have some additional code in custom actions. In this
code I need to refer to one of the install files but I cannot find how
to determine the path. For example, if the install CD is in the d:
drive and the user runs d:\setup.exe I want to know that it has been
run from d: (rather than e: or any other location) so that I can build
up the path to one of the folders on the CD.

I do not want to copy the file as part of the installation because it
is large and not required once installation is complete.

Can anyone help?

If you select the action to install your application and look at the
properties of it you can see the following property: CustomActionData Here
you type:/INSTALLDIR="[TARGETDIR]". In your installer class you can get the
parameter: Context.Parameters.Item("TARGETDIR"). This is how I find files in
the target directory. I believe the SOURCEDIR is what you want.

[JDS]

On 16 Dec, 12:52, Family Tree Mike
<[e-mail]:

Is your custom code (DLL) referenced within the install and commit phases?
Even if you don't do an "install" action, but just a "commit" as I usually
do, you need to do this. I got similar errors. I got errors during both
types of installs though.

I suspect then that when repairing, it does something slightly different
than when installing. I don't have any of my install projects here at home.
I will try to diagnose from my office computer at the next opportunity.- Hide quoted text -

- Show quoted text -

Yes, I only have code for commit. However, I tried adding a reference
to the install and still the same error on repair.

I have a form in my class (frmPostInstall) and all I have done in the
install action is to declare a new dummy form and then set it to
Nothing as follows:

Public Overrides Sub Install(ByVal stateSaver As
System.Collections.IDictionary)
Dim DummyForm As New frmPostInstall
Try
MyBase.Install(stateSaver)
DummyForm = Nothing
Catch ex As Exception
MsgBox("Custom action error on install: " & ex.Message)
End Try
End Sub

I don't know if this should be sufficient.

Thanks for your help.

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

"JDS" wrote:

On 16 Dec, 12:52, Family Tree Mike
<[e-mail]:

Is your custom code (DLL) referenced within the install and commit phases?
Even if you don't do an "install" action, but just a "commit" as I usually
do, you need to do this. I got similar errors. I got errors during both
types of installs though.

I suspect then that when repairing, it does something slightly different
than when installing. I don't have any of my install projects here at home.
I will try to diagnose from my office computer at the next opportunity.- Hide quoted text -

- Show quoted text -

Yes, I only have code for commit. However, I tried adding a reference
to the install and still the same error on repair.

I have a form in my class (frmPostInstall) and all I have done in the
install action is to declare a new dummy form and then set it to
Nothing as follows:

Public Overrides Sub Install(ByVal stateSaver As
System.Collections.IDictionary)
Dim DummyForm As New frmPostInstall
Try
MyBase.Install(stateSaver)
DummyForm = Nothing
Catch ex As Exception
MsgBox("Custom action error on install: " & ex.Message)
End Try
End Sub

I don't know if this should be sufficient.

Thanks for your help.

Bummer...

I got to work and tested a solution similar to what we are discussing, and
get the same error that you describe when I run the repair mode on my app. I
thought I had mine running. I will continue working this and if I find
anything, post back here. There must be some easy fix to this, you would
think...

[JDS]

On 17 Dec, 14:32, Family Tree Mike
<[e-mail]:

Bummer...

I got to work and tested a solution similar to what we are discussing, and
get the same error that you describe when I run the repair mode on my app. I
thought I had mine running. I will continue working this and if I find
anything, post back here. There must be some easy fix to this, you would
think...- Hide quoted text -

- Show quoted text -

Yes, you'd think ....

Thanks for having a look at this. Don't worry about progressing on my
account as the repair option is not really going to be that useful on
my app anyway and I will just include instructions to remove first if
it ever comes to that. However, it seems frustrating that it behaves
this way and I'm sure it will help someone else if there was an
answer.

Thanks again for your help.