Question : VB.Net Ineritance question

I am working in a VB.Net in Visual Studio 2008
I have a class in a DLL that I moved to another DLL.  This class inherited another class from a completely separate DLL.  When this class was in the first DLL, I could call functions from the inherited class in the separate DLL fine.  After I moved this class to its own DLL, I cannot reference functions, properties and subs from the first dLL.

I know it sounds like a juggling act, but my second DLL was getting so large and I wanted to break them apart into separate DLLs.

Example:
A.DLL  has a class called clsBase.  In this DLL, it has function  GetSettings

The second DLL has class called clsData...  it inherits clsBase from A.DLL   ...it has a bunch of functions of its own, but extends all the functions in the base class also.  (This worked fine until I moved this class into a 3rd DLL)

I moved clsData into a separate DLL and now any other apps that were using clsData can no longer get to functions,properties, subs in clsData.

Any ideas what I am doing wrong?   I am just trying to re-organize my DLL and cut it down on its size.

Thanks!

Answer : VB.Net Ineritance question

It turns out it was caused by my new DLL referencing the base DLL... With all of these being in 1 solution.  It required that it reference the project instead of the DLL directly.  As soon as I referenced the DLL project instead of directly to the DLL, Visual Studio stopped complaining about the references.   Kind of strange, but I guess for the dynamic debugger to work properly, it required this.

Thanks guys!