Guids should be unique. The only way to get this is by copying a project and forgetting to change it. VS.NET doesn't warn you of this, but behaves badly in subtle ways.

Ian MacLean wrote:
Is this the right patch ? if it is possible to have two valid projects with an identical guid should we use a different key for the hash table - perhaps a combination of the guid and the projectname ?

Ian

Hi all,

I found one very annoying feature/bug of <solution> task:

Projects (.csproj) are loaded into hashtable regarding their guid. But if
two projects with same guid are loaded, no error/warning is issued and one
of those projects disappears! Such projects could be created by copying and
renaming existing project into another file. Create new project with Visual
Studio generate new guid, so propability to create existing guid is
negligible.



Small patch to is attached. It checks this key violation rule and throws BuildException when it found one.

Regards,
Martin





------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn



------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to