Bugs item #1116862, was opened at 2005-02-05 16:19 Message generated for change (Comment added) made by exinor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1116862&group_id=31650
Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Submitted By: Manu (manudea) Assigned to: Nobody/Anonymous (nobody) Summary: Different projects with same guid in a solution fail Initial Comment: Apply to nant 85 and 84 (maybe others) If you have 2 projects with same guid in a visual studio solution only the latter one is built. The first one is ignored. I think this is a Nant bug because VStudio builds just fine, so Nant should, IMHO, build in the same way as Vstudio does. Assuming that guid uniqueness exists in Vs solution it seems a wrong assumpton. If it would VS would complaint about this an do not build. ---------------------------------------------------------------------- Comment By: Nicklas Norling (exinor) Date: 2005-03-05 21:18 Message: Logged In: YES user_id=949257 Nant used to give NullReferenceException when GUIDs where not unique. I submitted a patch that writes a (hopefully) descriptive error when this is encountered and the compile should stop. Isn't the error still there? I think Nant could possibly try to match the project names if GUIDs are not unique and get a bit further, but as pointed out it has to be considered a bug that VS isn't alerting the user, or recreates the duplicate GUID. /Nicke ---------------------------------------------------------------------- Comment By: Alex Hildyard (ahildyard) Date: 2005-02-21 16:05 Message: Logged In: YES user_id=1114643 I actually think NAnt's behaviour is more "correct" than Visual Studio. Assuming that GUIDs are supposed to provide a mapping between project files and the project references within a solution file, I regard Visual Studio as defective because it will often continue to build solutions perfectly happily even when the two GUIDs don't match. This is clearly a recipe for disaster, since at some point Visual Studio's often inspired guesswork matching projects to solutions is going to be wrong. However, I agree that NAnt's behaviour isn't perfect. I would like to see NAnt throw an error if it finds duplicate GUIDs; I agree that silently building one of the projects and ignoring the other isn't the best behaviour. But I don't think reproducing Visual Studio's behaviour is the way to go. Just my tuppenceworth. Regards, Alex ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1116862&group_id=31650 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
