Hello, I think, we have some time, since xBuild seems to be in pre-alpha stage. But interestingly, MSBuild is using Microsoft.Build.* namespace - xBuild mimics this as well? Seems little ugly to me.
> The difference between xBuild and MSBuild is only the platform, they both use the same file layout en structure. What I don't know is what happens when people create custom tasks in msbuild. Because the MSBuild file is also the project file would VS2005 leave them, move them, modify them? What happens when you want to run in in Mono? VS lives happily with that. I use it for some small tweaks (like copy output there and there...). Wish it has nant syntax - I'd use it more :-) There are also VS extensions (like VSIP or WebApplication) which registers new tasks and use them in their projects. Basically, VS itself do not read project files directly - it uses MSBuild to read fileset of input files (itemgroup in terms of msbuild) and some properties (propertygroup). There are some limitations to property conditioning, if you want use it under VS, but under normal case, it just works. Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
