path to third party libraries

[a.kamroot]

Hi

I am new to c# and the .NET environment so I might not be using the
right terminology. However. I have downloaded Codeplex's public domain
Logging files (and assemblies) [from http://www.codeplex.com/PublicDomain].

I have installed the assemblies, and included the using PublicDomain
directive in my path. However, the compile fails since the complier
can't find the assembly. I suspect I need to put in a fully qualified
path to the libaries.

My question is how do I do that - make the compiler aware of the
location of third party assemblies?

I am willing to read up on this, if someone can point me to the right
URLs.

Thanks in advance.
Kamroot.

 

[Graeme Bradbury]

Are you using an IDE or just using the framework with the command
line?

If it's command line the only resource i know is
http://msdn2.microsoft.com/en-us/library/78f4aasd(VS.80).aspx

If it's VS2005 then have you added a reference to the assemblies in
the project itself?

 

[Rad [Visual C# MVP]]

Hi

I am new to c# and the .NET environment so I might not be using the
right terminology. However. I have downloaded Codeplex's public domain
Logging files (and assemblies) [from http://www.codeplex.com/PublicDomain].

I have installed the assemblies, and included the using PublicDomain
directive in my path. However, the compile fails since the complier
can't find the assembly. I suspect I need to put in a fully qualified
path to the libaries.

My question is how do I do that - make the compiler aware of the
location of third party assemblies?

I am willing to read up on this, if someone can point me to the right
URLs.

Thanks in advance.
Kamroot.

You need to add a reference to the new assemblies in your project so
that the compiler can find them during the compilation process.
Alternatively you can add them in the Global Assembly Cache, but if
you go down this road you need to factor this fact into your
deployment, as your routine will as well need to add the assemblies to
the GAC as well