Hi Hadzramin,
I've finally noticed that you are building a VB.NET problem, and now I
understand what the actual problem is.
I've actually documented this strange behavior of VB.NET in our code :
/// <para>
/// Apparently, there's some hack in VB.NET that allows a type to be
used
/// that derives from a type in an assembly that is not referenced
by the
/// project.
/// </para>
/// <para>
/// When building from the command line (using vbc), the following
error
/// is reported "error BC30007: Reference required to assembly 'X'
/// containing the base class 'X'. Add one to your project".
/// </para>
/// <para>
/// Somehow VB.NET can workaround this issue, without actually
adding a
/// reference to that assembly. I verified this with both VS.NET
2003 and
/// VS.NET 2005.
/// </para>
/// <para>
/// For now, we have no other option than to return all assembly
/// references of the referenced project if the parent is a VB.NET
/// project.
/// </para>
As a result of this behavior, we have no other choice than to add assemblies
that are referenced by a certain project, as references to a project that
references this project.
Meaning, if project A references assemblies A1 and A2, and project B
references project A then we need to add the output of project A AND
assemblies A1 and A2 as references when building project B.
Now, when both project A and project B reference the same assembly you run
into the problem that you're describing.
For C# we don't have this problem, as we don't have to include indirect
references when building C# projects. That's why I was unable to reproduce
your problem.
I'd really like to know how MS works around this in MSBuild (I've verified
that they do). I'll ask Alex Kipman when I find some time to prepare a repro
for this and text on this topic.
For now, submit a bug report including a repro for this issue. I'll then
look into it as soon as possible.
Gert
> -----Original Message-----
> From: Hadzramin AR [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: donderdag 23 december 2004 9:41
> To: 'Castro, Edwin Gabriel (Firing Systems Engr.)'; 'Gert Driesen'
> Cc: nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] RE: Nant & COM interop
>
>
> Hi Edwin & Gert,
>
> Edwin, I tried the files that you send earlier and it works.
> But, the same error occurred when trying with my solution.
>
> - error BC30560: 'DataWrap' is ambiguous in the namespace 'VPDal5'.
>
> See attachment for details.
>
> Anything else I can do to troubleshoot this error?
>
> Thanks.
>
> Hadzramin
> -----Original Message-----
> From: Castro, Edwin Gabriel (Firing Systems Engr.)
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 23, 2004 4:16 AM
> To: Castro, Edwin Gabriel (Firing Systems Engr.); Gert Driesen;
> [EMAIL PROTECTED]; nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] RE: Nant & COM interop
>
> Hi Hadzramin,
>
> I attached a zip file including what sounded like a minimal
> repro for your
> problem. Like Gert, I also did not find anything wrong with
> this type of
> repro. Could you look it over and figure out 1) if it works
> for you and 2)
> if there's something you were doing that we did not do.
>
> I'm using NAnt 0.85 (Build 0.85.1798.0; dev; 12/3/2004). As
> usual, if you're
> using an old version of NAnt (mine is almost 20 days old!)
> and you have
> problems the first thing to try is to check the newest and
> greatest nightly.
> I also recommend that once you find a version that works
> (like I did) and
> don't upgrade unless necessary (like to get new/improved
> functionality or
> bug fixes).
>
> --Edwin
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:nant-users-
> > [EMAIL PROTECTED] On Behalf Of Castro, Edwin Gabriel
> (Firing
> > Systems Engr.)
> > Sent: Wednesday, December 22, 2004 11:29 AM
> > To: Gert Driesen; [EMAIL PROTECTED];
> nant-users@lists.sourceforge.net
> > Subject: RE: [Nant-users] RE: Nant & COM interop
> >
> > Interestingly, I used to have this problem too. In my case
> I had two
> > projects (A and B) with one project dependent on the other
> (A depends
> on
> > B). Both projects referenced a COM assembly (C.exe via
> interop.c.dll)
> > and I used to get the access errors which I think occurred
> because the
> > second project was trying to copy over the C.dll that was already in
> the
> > build directory.
> >
> > I ended up refactoring my stuff so only one project needed to
> reference
> > the COM assembly.
> >
> > Fortunately, I think VS.NET (2003 at least) has a similar
> problem. It
> > turns out that if you try to rebuild a solution that includes a
> project
> > that references a COM assembly which is another project in the
> solution
> > (that is you don't reference the COM assembly as a project in the
> > solution but through the registry) then you get weird errors because
> it
> > can't delete the COM assemblies... It's a weird corner case (I
> believe)
> > that happens in our setup because of a very long history of doing
> things
> > weird (I'm new to this team) so I've needed to jump through some
> amazing
> > hoops to add an automated test suite to our code base.
> >
> > I'll try to simulate Hadzramin's scenario locally and see
> what I find
> > out. You must have a very well behaved setup Gert! :-)
> >
> > --Edwin
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:nant-users-
> > > [EMAIL PROTECTED] On Behalf Of Gert Driesen
> > > Sent: Wednesday, December 22, 2004 11:16 AM
> > > To: [EMAIL PROTECTED]; nant-users@lists.sourceforge.net
> > > Subject: RE: [Nant-users] RE: Nant & COM interop
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED] On Behalf Of
> > > > [EMAIL PROTECTED]
> > > > Sent: woensdag 22 december 2004 8:42
> > > > To: 'Gert Driesen'; nant-users@lists.sourceforge.net
> > > > Subject: RE: [Nant-users] RE: Nant & COM interop
> > > >
> > > > Hi Gert,
> > > >
> > > > After I stuck with the <solution> task last time, I did
> not test &
> > > > explore further with the approach.
> > > > The last thing I remember, since every projects
> referenced to the
> > > > same COM e.g ADODB.dll (ADO 2.6), the solution try to copy the
> > > > same dll to the build directory, that causing error (no
> access I
> > > > believe).
> > > >
> > > > If you want to simulate it, try to create a solution with 2
> > > > projects (1 web project & 1 class project) Both project have
> > > > references to ADO 2.6.
> > >
> > > I cannot seem to reproduce this issue here. Would you consider
> sending
> > me
> > > a
> > > repro anyway ?
> > >
> > > Thanks !
> > >
> > > Gert
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > 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://productguide.itmanagersjournal.com/
> > > _______________________________________________
> > > Nant-users mailing list
> > > Nant-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nant-users
> >
> >
> > -------------------------------------------------------
> > 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://productguide.itmanagersjournal.com/
> > _______________________________________________
> > Nant-users mailing list
> > Nant-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nant-users
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.820 / Virus Database: 558 - Release Date: 12/20/2004
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.820 / Virus Database: 558 - Release Date: 12/20/2004
>
>
>
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
