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
