I'm not sure I understand why you can't keep them in a solution. Maybe
I'm just tired today, but I don't see a circular reference problem with
the project dependencies that you have described.
You might want to just lock down your version numbers so developers have
to change them rather than changing them every time you recompile.
As for the AssemblyInfo.cs thing, to make that work you'll still have to
lock down your version numbers. Delete the following line from the
AssemblyInfo.cs file of each project.
[assembly: AssemblyVersion("1.0.0.0")]
Then add just that line to a separate file. That file then becomes part
of projects A, B, and C, and when you build the assemblies they will all
be guaranteed to have the same version number.
Add the file by right-clicking on the project, select Add->Existing
Item. Browse to the file, but don't click Open. Instead click the arrow
next to Open and select Link File. That way you don't create three
copies of the file but instead a shortcut to a single copy of the file.
You may want to check out this document. If memory serves it discusses
this technique.
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=
94FDB8C8-5A87-4545-AF75-6053F32C7ECA
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pradeep
Rapole
Sent: Tuesday, November 30, 2004 10:18 AM
To: [EMAIL PROTECTED]
Subject: [Nant-users] VS.NET and NAnt version issue
Hi,
Herez the scenario I have. Suppose I have projects A, B and C.
Project B
uses the out put from Project A and Project C uses the output from
project
B. So I can't keep them in a solution in VS.NET. I am using NAnt for
building. Everything seems to be going good except the version problem.
Two different developers working on thier machines when they do
builds
and check in thier codes, since each of them is likely to have run
different number of builds before checking in their stuff, we are having
issues where different projects have different version numbers and even
though the changes made by one developer might be the latest one, but
if
the other developer has run more builds on his machine, so the changes
from
the former wont' be taken.
someone here adviced me to add a file AssemblyVersionInfo.cs at the
main
level and all the other AssemblyInfo.cs files would take its version
from
this file. Can anyone give me more, preferably as much as you can, on
this?
Thanks in advance.
Pradeep
-------------------------------------------------------
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
[EMAIL PROTECTED]
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
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
