Problem with one DLL using another DLL

[wolfo]

Hi!
My aspx-project uses the dll "a.dll" for some calculations. I added a reference to this dll in my project - so I can use most of the functions provided by the dll. Some functions in "a.dll" make use of another dll ("b.dll") though. When I try to call these functions, an error occurs, saying that "b.dll" was not found. When I try to add a reference to b.dll, this doesn't work - an error occurs saying that "b.dll is not a valid assembly or COM component".

In order to solve my problem, I assume that I have to determine the place where my application should look for additional project components. I believe that this could either be done by
- setting a path to b.dll somewhere in my c#-code
or
- editing some configuration file (that contains information about the files in my project).

I'm not sure if my assumptions are right and if yes, how I could realize them.
Thanks to anyone who can give some hints how to solve this problem.

wolf

[Miha Markic [MVP C#]]

Hi,

"wolfo" <an*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com...

Hi!
My aspx-project uses the dll "a.dll" for some calculations. I added a

reference to this dll in my project - so I can use most of the functions
provided by the dll. Some functions in "a.dll" make use of another dll
("b.dll") though. When I try to call these functions, an error occurs,
saying that "b.dll" was not found. When I try to add a reference to b.dll,
this doesn't work - an error occurs saying that "b.dll is not a valid
assembly or COM component".

Well, is it? Valid, I mean?

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

[Miha Markic [MVP C#]]

Hi,

"wolfo" <an*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com...

Hi!
My aspx-project uses the dll "a.dll" for some calculations. I added a

reference to this dll in my project - so I can use most of the functions
provided by the dll. Some functions in "a.dll" make use of another dll
("b.dll") though. When I try to call these functions, an error occurs,
saying that "b.dll" was not found. When I try to add a reference to b.dll,
this doesn't work - an error occurs saying that "b.dll is not a valid
assembly or COM component".

Well, is it? Valid, I mean?

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com