Brass,
please, do not blame me. You could have solutions, but I wrote about __set
of projects__. Thats is different beast. See mine previous example or just
simple
<solution>
<projects>
<include name="**/*.csproj"/>
</projects>
</solution>
There is no (simple) way how to do this in msbuild (with correct build order
etc.)
If you do not need this feature and are satisfied with simple <exec
program="msbuild.exe"/>, ok. But others have different needs. As I don't use
<nunit> task but <exec>ing nunit-console.exe. And I do not blame <nunit>
authors that their task is not usable. It is in some cases. Maybe not in
mine, but they certainly helped many other users with unit testing. As well
as I hope <msbuild-*> tasks would help with msbuild integration. If not, I'd
simply wrote mine own NAnt and do not share with others.
Martin Aliger
> -----Original Message-----
> From: Brass Tilde [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 17, 2006 2:43 PM
> To: Martin Aliger; 'Dominik Guder';
> nant-developers@lists.sourceforge.net
> Subject: Re: [nant-dev] Re: Continuing work on <msbuild-solution>
>
> > As Brass wrote, there usually is not a problem even with <exec>ing
> > msbuild.exe. Despite it's not much elegant, there are some caveats.
> > One,
> > which was show-blocker for me, msbuild is unable to build set of
> > projects like <solution> is.
>
> Completely untrue. I have several solutions that contain
> multiple projects. MSBuild builds them all just fine.
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
