Locating files

  • Thread starter Thread starter John
  • Start date Start date
J

John

Hi

I have two applications and one needs to access the files of the other. The
problem is that on my development machine they are in one set of folders but
on the end user's machine they would be in different folders. Is there a
safe way for one app to locate folder (and files) of the other app, both on
the development and target machines?

Thanks

Regards
 
* "John said:
I have two applications and one needs to access the files of the other. The
problem is that on my development machine they are in one set of folders but
on the end user's machine they would be in different folders. Is there a
safe way for one app to locate folder (and files) of the other app, both on
the development and target machines?
Click to expand...

You can write the path of your application into a registry key (class
'Microsoft.Win32.Registry') and read this key from the other application.
 
Thanks. I think you mentioned the place in registry where I can create my
own keys. Care to give it again?

Thanks

Regards
 
How can I get the setup to add the user selected installation path into the
registry entry?

Thanks

Regards
 
* "John said:
How can I get the setup to add the user selected installation path into the
registry entry?
Click to expand...

You can do this the first time when your application starts if there is
no easy way to do that with a setup (I don't know if this is possible
with a setup project).
 
You can do this the first time when your application starts if there is
no easy way to do that with a setup (I don't know if this is possible
with a setup project).
Click to expand...

It is (and is suprisingly easy!):

1) Create a setup application
2) Select "View Registry"
3) Add a new key & string value
4) Specify [TARGETDIR] as the value.
 
* _Andy_ said:
You can do this the first time when your application starts if there is
no easy way to do that with a setup (I don't know if this is possible
with a setup project).
Click to expand...

It is (and is suprisingly easy!):

1) Create a setup application
2) Select "View Registry"
3) Add a new key & string value
4) Specify [TARGETDIR] as the value.
Click to expand...

Thanks for the info. I didn't know that.
 
* _Andy_ said:
How can I get the setup to add the user selected installation path into the
registry entry?

You can do this the first time when your application starts if there is
no easy way to do that with a setup (I don't know if this is possible
with a setup project).
Click to expand...

It is (and is suprisingly easy!):

1) Create a setup application
2) Select "View Registry"
3) Add a new key & string value
4) Specify [TARGETDIR] as the value.
Click to expand...

Thanks for the info. I didn't know that.
Click to expand...

I've just finished building my first .Net setup application, and I was
in shock at how simple it was. I learned InstallShield script, for
God's sake! I remember implementing my own setup application using
SETUP.DLL... installing DAO, no less! *That* was a PITA!
I'm loving .Net more and more every day!

Rgds,
 
* _Andy_ said:
You can do this the first time when your application starts if there is
no easy way to do that with a setup (I don't know if this is possible
with a setup project).

It is (and is suprisingly easy!):

1) Create a setup application
2) Select "View Registry"
3) Add a new key & string value
4) Specify [TARGETDIR] as the value.
Click to expand...

Thanks for the info. I didn't know that.
Click to expand...

I've just finished building my first .Net setup application, and I was
in shock at how simple it was. I learned InstallShield script, for
God's sake! I remember implementing my own setup application using
SETUP.DLL... installing DAO, no less! *That* was a PITA!
I'm loving .Net more and more every day!
Click to expand...

If you have a look at the comments about VS.NET's setup templates, most
people say that the documentation is really bad and it's really hard to
use.

;-)
 
Back
Top