I think I understand. Each developer has a bunch of reference directories that are set up in VS.NET, right? You're right - we would likely need to add a <references> tag to the solution task to handle this situation.

Matt.

Martin Aliger wrote:

Odd...  We simply check in .csproj files and leave .csproj.user files on
each machine individually.  We haven't had any issues with this.

Are you perhaps talking about 3rd party references? Or GAC references?



no - normal references to assemblies. Unfortunattely we do not use CVS or similar system and every developer has another directory tree. A lot of us do not have sources from all assemblies and references pre-built .dlls. This result is scheme, where one developer writes assembly "Gordic.General" and another one "Gordic.Win32" which is dependant on General <Reference Name = "Gordic.General" AssemblyName = "Gordic.General" HintPath = "..\dll\Gordic.General.dll" />

But on build server no path ..\dll exists and nant failed with
              BUILD FAILED
              Couldn't find referenced assembly
'C:\temp\src\dll\Gordic.General.dll'.

This is logical but imposible to solve right now. Maybe solution is to
create some attribute to Solution task to override references path? (like
outputdir)

What is your ideas?

Thanks,
Martin




------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers







-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to