PC Review


Reply
Thread Tools Rate Thread

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

 
 
Paul Linville
Guest
Posts: n/a
 
      27th Dec 2007
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
 
Reply With Quote
 
 
 
 
Family Tree Mike
Guest
Posts: n/a
 
      27th Dec 2007
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.


"Paul Linville" wrote:

> 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

 
Reply With Quote
 
Paul Linville
Guest
Posts: n/a
 
      27th Dec 2007
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".

"Family Tree Mike" wrote:

> 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.
>
>
> "Paul Linville" wrote:
>
> > 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



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
At wits end dealing with "Assembly's manifest does not match assembly reference". Need help understanding the process. Richard Lewis Haggard Microsoft C# .NET 3 26th Feb 2006 02:14 AM
Assembly loading error "manifest definition... does not match assembly reference" Gary McGill Microsoft Dot NET 3 24th May 2005 02:58 PM
"Reference required to assembly 'RootLevel' containing the type 'RootLevel.Root'. Add one to your project." Good Enchiladas Microsoft VB .NET 7 22nd Apr 2004 09:57 PM
"Reference required to assembly 'RootLevel' containing the type 'RootLevel.Root'. Add one to your project." Good Enchiladas Microsoft Dot NET 1 22nd Apr 2004 01:12 PM
"Reference required to assembly 'RootLevel' containing the type 'RootLevel.Root'. Add one to your project." Good Enchiladas Microsoft Dot NET Framework 0 22nd Apr 2004 12:41 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 12:19 PM.