I've been working on something along the same lines, except that we're doing C# and C++. Essentially, there's a build file which uses the <style> task to convert a .csproj file to .build, then uses the <nant> task to build it. I'm amusing myself so much with this that I'll probably finish it whether or not anybody else would actually use it :-)
One other approach that I've thought of would be to do this via the VS Automation API or a VS.NET macro. That API's a little flaky, but I think it gives you enough to mirror a solution in a .build.
-----Original Message-----
Actually,
What we did is write an xslt transformation that converts a vbproj to a nant build file. So, in our scenario the master build file performs the transform, which outputs a .build file, executes it, then returns control back to the master build file.
It works really well, and the transform is blazingly fast...
Don
-----Original Message-----
From: Kevin Dente [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 3:51 PM
To: Brad Wilson; NAnt Developers
Subject: Re: [nant-dev] New task idea
True - but then you actually need the IDE installed on
that machine. With the CSPROJ task, you only need the
free C# compiler (as in, you don't need a VS.Net
license for your build machine).
The <devenv> task is really just the <exec> task.
--- Brad Wilson <[EMAIL PROTECTED]> wrote:
> Kevin Dente wrote:
>
> > [...] a task that builds directly from the VS.Net
> project file would be
> > even nicer. Of course, VBPROJ and VCPROJ tasks
> would likely follow.
>
> All of the above can be done from devenv.com (open a
> command prompt and type
> "devenv /?" for command line options). A <devenv>
> task sounds like a better
> fit. :)
>
> Brad
>
> --
> Read my web log at http://www.quality.nu/dotnetguy/
