Bugs item #1237756, was opened at 2005-07-13 15:02
Message generated for change (Settings changed) made by abolourian
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1237756&group_id=31650
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tasks
Group: 0.85
>Status: Closed
>Resolution: Invalid
Priority: 3
Submitted By: Ali Bolourian (abolourian)
Assigned to: Nobody/Anonymous (nobody)
Summary: Solution task fails compiling ...
Initial Comment:
In VS.NET 2003 Project A has a reference to assmebly
X that is depending to .NET 1.0 and I don't have .NET
1.0 on my machine. This project compiles and works
with no problem both in NAnt and VS.NET.
Now project B in a different solution has a reference to
assembly A, this project fails to build. the error is:
Error resolving module references of 'A.dll'.
File or assembly name X.dll, or one of its
dependencies, was not found.
Thanks,
Ali B
----------------------------------------------------------------------
Comment By: harrie (harrie_thijssen)
Date: 2005-08-20 08:04
Message:
Logged In: YES
user_id=1332164
Hi, I have experieced the same problem.
The workaround i found is to set the reference property "Copy
local" in the project to "false" for this particular assembly.
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2005-07-15 11:47
Message:
Logged In: YES
user_id=707851
Ali,
Can you please attach that repro ?
Thanks !
----------------------------------------------------------------------
Comment By: Ali Bolourian (abolourian)
Date: 2005-07-14 11:17
Message:
Logged In: YES
user_id=921564
I found out that module X had some dependencies to other
modules and they didn't show up even in Reflector and
therefore didn't come with X to project A's set of bin files. So
project B fails to build because
module = Assembly.LoadFrom(moduleName);
fails to load X in
NAnt.VSNet.ReferencesResolver.AppendReferencedModulesL
ocatedInGivenDirectory()
So now the main problem is that:
If a module has any hidden dependencies on X, VS.NET
builds B successfully and NAnt doesn't.
----------------------------------------------------------------------
Comment By: Ali Bolourian (abolourian)
Date: 2005-07-13 15:06
Message:
Logged In: YES
user_id=921564
By the way, project B builds successfully in VS.NET but not
in NAnt.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1237756&group_id=31650
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
