Bugs item #1174976, was opened at 2005-04-01 20:38
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1174976&group_id=31650

Category: None
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: ve1 (vilas_ekbote)
Assigned to: Nobody/Anonymous (nobody)
Summary: For COM dlls - error BC30652: Reference required to assembly

Initial Comment:
This is happening in the nant-0.85-rc2 and
nantcontrib-0.85-rc2.

How to reproduce:

1. Add a reference to a COM dll in my case I had
reference to three COM dlls in my VB.NET project:
MSXML2,- COMSvcsLib and one more vb6 dll.

2. I had a nant file that built the solution that
mostly had VB.NET projects using <solution> task.

3. When I ran the nant build I encountered following
errors [enclosed in star lines]:

*******************************************************
error BC30652: Reference required to assembly
'COMSVCSLib' containing the type
'COMSVCSLib.ObjectContext'. Add one to your project.
 [solution] 
 [solution]             here was the line from my code
that was calling the vb6 dll [taken out for security
reasons]
 [solution]            
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 [solution] [name and line number of the file where it
happened - taken out for security reasons] : error
BC30652: Reference required to assembly 'MSXML2'
containing the type 'MSXML2.IXMLDOMDocument2'. Add one
to your project.
 [solution] 
 [solution]             here was the line from my code
that was calling the vb6 dll [taken out for security
reasons]
 [solution]                                           
 ~~~~~~~~~~~~~~~~~~                       
 [solution] Build failed.

*******************************************************

I did find the workaround after beating my head on it
for sometime, here it is hope someone finds it helpful:

This typically only happens to COM library references
in vb.net projects. This might be a VS.NET problem see
the kb from microsoft here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;818411


The workaround to this problem is to:
1. generate Interop.* files first by adding reference
to appropriate DLLS
2. then backup the Interop.* files in some other folder
3. Remove the references to COM libraries
4. copy the backed up Interop.* files to bin folder again
5. Now add references to Interop.* files not the
original COM libraries
6. if you have the source control and nant is getting
files on the fly from source control checkin the
Interop.* files in bin folder



----------------------------------------------------------------------

>Comment By: Gert Driesen (drieseng)
Date: 2005-04-01 23:08

Message:
Logged In: YES 
user_id=707851

Can you attach a small repro for this issue ?

Thanks !

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1174976&group_id=31650


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to