Brad Wilson wrote:
well they won't fix it because 2.0 projects will be MSBuild files and therefore a completely different format.It's too late, really. Even if they fix this for 2.0, the <solution> task will need to parse 1.0 and 1.1 project files far into the future, and thus the code will need to exist. It's, ironically, less work if they don't fix it, since it will prevent needing to have two codepaths (one for 1.x project files and one for 2.0+ project files).
Ian
FWIW, I'm sure Slingshot probably chokes on this, too, unless they have a work-around, since they'll be stuck with the same problem. It's probably worth mentioning on whatever list is used for Slingshot maintenance about this bug.
- Brad
On Mon, 6 Dec 2004 09:46:06 -0500, Ryan Cromwell
<[EMAIL PROTECTED]> wrote:
Has anyone contacted either the MSDN newsgroups or MS support to
report what very well could be a bug? Then everyone would be happy :)
-------------------------------------------------------
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
