how to get the path of an installed DLL of VS .NET Add-in

[Tee]

Hi,

I am creating a VS .NET Add-in. There's an xml config file that will
installed to same folder as the DLL is installed.
The installation path probably is something like C:\Program Files\Company
Name\VSAddin

From the VS .NET Add-in, it needs to locate the xml config file and
read/write data to it.
Anyone know how can I get the folder location by coding?
I tried Application.StartupPath and also
AppDomain.CurrentDomain.BaseDirectory, but none of them just work.
What I get is something like C:\Program Files\Visual Studio 2003\Common\IDE
....

Can anyone help?

Thanks.
Regards,
Tee

[Arne Janning]

Hi Tee!

"Tee" schrieb

I am creating a VS .NET Add-in. There's an xml config file that will
installed to same folder as the DLL is installed.
The installation path probably is something like C:\Program Files\Company
Name\VSAddin

From the VS .NET Add-in, it needs to locate the xml config file and
read/write data to it.
Anyone know how can I get the folder location by coding?
I tried Application.StartupPath and also
AppDomain.CurrentDomain.BaseDirectory, but none of them just work.
What I get is something like C:\Program Files\Visual Studio
2003\Common\IDE

If you have a reference to your assembly you can use Assembly.Location.
However I don't think it is a good idea to store the config-file in the
application-folder because that would require write-permissions on that
folder. Users normally don't have write-permissions on the
application-folder. Better use the ApplicationData-folder for a specific
user.

Cheers

Arne Janning

[Tee]

Hi Arne,

Thanks for your reply.
Can you provide me with a little bit more of information?

What do you mean by I have reference to the assembly ?
My previous question was how the add-in detect it's own DLL location ...
and the Assembly.Location is under what namespace?

Thanks.
Tee
"Arne Janning" <sp*****************@msn.com> wrote in message
news:Oj**************@TK2MSFTNGP11.phx.gbl...

Hi Tee!

"Tee" schrieb

I am creating a VS .NET Add-in. There's an xml config file that will
installed to same folder as the DLL is installed.
The installation path probably is something like C:\Program Files\Company Name\VSAddin

From the VS .NET Add-in, it needs to locate the xml config file and
read/write data to it.
Anyone know how can I get the folder location by coding?
I tried Application.StartupPath and also
AppDomain.CurrentDomain.BaseDirectory, but none of them just work.
What I get is something like C:\Program Files\Visual Studio
2003\Common\IDE

If you have a reference to your assembly you can use Assembly.Location.
However I don't think it is a good idea to store the config-file in the
application-folder because that would require write-permissions on that
folder. Users normally don't have write-permissions on the
application-folder. Better use the ApplicationData-folder for a specific
user.

Cheers

Arne Janning

[Arne Janning]

Hi Tee!

"Tee" schrieb

Thanks for your reply.
Can you provide me with a little bit more of information?

What do you mean by I have reference to the assembly ?
My previous question was how the add-in detect it's own DLL location ...
and the Assembly.Location is under what namespace?

Import the System.Reflection-namespace.

Let's say you have defined a class in your assembly: MyAddinClass

You can get a reference to the assembly (the DLL) in which this class is
defined:

Assembly a = Assembly.GetAssembly(typeof(MyAddinClass));

Now a.Location contains the full-path to your DLL:

Debug.WriteLine(a.Location);

Cheers

Arne Janning

[Tee]

Arne,

Thanks for the code, it works.
But while waiting you or someone else to reply, I found that
Assembly.GetExecutingAssembly().Location work the same.

Between this 2 methods, what's the differences ?

and which to go with? any idea?

Thanks.

Tee

"Arne Janning" <sp*****************@msn.com> wrote in message
news:en**************@TK2MSFTNGP12.phx.gbl...

Hi Tee!

"Tee" schrieb

Thanks for your reply.
Can you provide me with a little bit more of information?

What do you mean by I have reference to the assembly ?
My previous question was how the add-in detect it's own DLL location ...
and the Assembly.Location is under what namespace?

Import the System.Reflection-namespace.

Let's say you have defined a class in your assembly: MyAddinClass

You can get a reference to the assembly (the DLL) in which this class is
defined:

Assembly a = Assembly.GetAssembly(typeof(MyAddinClass));

Now a.Location contains the full-path to your DLL:

Debug.WriteLine(a.Location);

Cheers

Arne Janning

[Arne Janning]

Hi Tee!

"Tee" schrieb

Thanks for the code, it works.
But while waiting you or someone else to reply, I found that
Assembly.GetExecutingAssembly().Location work the same.

Between this 2 methods, what's the differences ?

and which to go with? any idea?

If you for example develop a Windows.Forms-application and have one EXE
(GUI) and one DLL (Business Objects) then using
Assembly.GetExecutingAssembly().Location in your DLL will contain the path
for the EXE-file. I wasn't sure if the
Assembly.GetExecutingAssembly().Location of an add-in-dll would point to the
hosting application or not, this is why I didn't make this proposition. But
if it works as well, even better.

In contrast Assembly.GetAssembly(Type t) can get the assembly for every
known .NET-Type at runtime. E.g. Assembly.GetAssembly(typeof(int)).Location
will give you the path for the mscorlib.dll.

Cheers

Arne Janning

[Tee]

Arne,

Thanks a lot for all your help.
You rock! Cheers! :)
Thanks,
Tee
"Arne Janning" <sp*****************@msn.com> wrote in message
news:uT**************@TK2MSFTNGP14.phx.gbl...

Hi Tee!

"Tee" schrieb

Thanks for the code, it works.
But while waiting you or someone else to reply, I found that
Assembly.GetExecutingAssembly().Location work the same.

Between this 2 methods, what's the differences ?

and which to go with? any idea?
If you for example develop a Windows.Forms-application and have one EXE
(GUI) and one DLL (Business Objects) then using
Assembly.GetExecutingAssembly().Location in your DLL will contain the path
for the EXE-file. I wasn't sure if the
Assembly.GetExecutingAssembly().Location of an add-in-dll would point to

the hosting application or not, this is why I didn't make this proposition. But if it works as well, even better.

In contrast Assembly.GetAssembly(Type t) can get the assembly for every
known .NET-Type at runtime. E.g. Assembly.GetAssembly(typeof(int)).Location will give you the path for the mscorlib.dll.

Cheers

Arne Janning