"reference required to assembly" But reference does exist in vbpro

  • Thread starter Thread starter Paul Linville
  • Start date Start date
P

Paul Linville

I have a solution that has both c# and vb.net projects. Visual Studio 2005
sp1.

One of the lower level asseblies "Utils.csproj" is a c# project that
references a 3rd party dll "Framework.dll".

Other c# projects reference Utils.csproj (Utils.dll) just fine. However
when referencing the Utils.csproj in a vb project in the same solution and
trying to access a class of the Utils.csproj classes I get the error
"reference required to assembly xxx please add one to your project".

So in VBUnitTests.vbproj when calling

Dim x as ObjectA

And
Utils.ObjectA inherits from FrameWork.VirtualClass

That is when I get the "Reference required to Framework.dll"

That particular assembly IS referenced. I see it in the referenced library
list and intellisense works with all other classes I have tried. It only
failes with the Utils class that inherits from a virtual class in the
framework.dll
 
Do you have a reference to Framwork.dll in your vbUnitTests.vbproj? It's not
clear from what you wrote, but it sounds like that is missing.
 
Yes. It is definatly referenced. I can use intellisense to look at all of
Framework members etc. I can even declare SIFMessageBase class (the virtual
class that is being inherited by the SIFMessageInfo class in the Utils.dll).

I can also use all the classes in Utils.dll EXCEPT FOR the Class
(SIFMessageInfo) that inherits from SIFMessageBase. As soon as I try to
declare a SIFMessageInfo class I get the "reference required to assembly".
 
Back
Top