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
Brad Wilson wrote:
Kevin Dente wrote:
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).
What part of the SDK creates and/or interprets .csproj
At my company, we want to use NAnt for its build
automation features, but we're also a bunch VS.Net
users. Having to create a separate NAnt project is a
bit of drag - even worse is keeping it synchronized
with the VS.Net project as it evolves. Slingshot
helps, of course, but a task that
What part of the SDK creates and/or interprets
.csproj files?
It doesn't. In order to create the .csproj, you need
VS.Net. At build time, the CSPROJ task would interpret
that file directly (no devenv needed) and call the
freely-available-in-the-SDK csc compiler. While the
developers would use
From a different point of view a task that would create a .xxproj from a
portion of a build file would also be very cool.
I've been using nant to build C++ projects but I like working in the VS IDE.
I use nant for all the building via an external tool hookup but I also have
a fake project so
i tried this out a while back and i had a rather big problem. i
couldn't capture the output from devenv.exe... i did this by
subclassing the exec task, and it just wouldn't work. i'll see if i
can dig up the code.. it's really been a while.
--b
- Original Message -
From: Brad Wilson
this is a reply to the whole topic...sorta...I think :)
I would like to see NAnt fully integrated into the MS IDE. I've put a little
thought into it, but we are in death march mode and I haven't really had any
time to pursue it. Something along the lines of:
1) Create project.
2) Write code.
3)
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
Title: RE: [nant-dev] New task idea
no. http://msdn.microsoft.com/vstudio/vsip/qa.aspI
don't think this would be anything more than an add-in. As far as the
difficulty, I'm not sure. The difficulty and time to develop isn't too big of a
deal though, I will have plenty of time as soon as my
Someone has already done it. Check out
http://nantcontrib.sf.net/NAntAddinSetup.msi
Oops... I totally forgot about AddIns, guess I was a little quick to
jump on the most complicated solution.
Once I get a little more bandwidth (Aug. 5th app goes to prod), I'd be
willing to work on
One of the features I wanted to add to the NAnt VS.Net Addin that Jayme
wrote was the ability to create a NAnt build file from the current
project. It would be pretty simple using slingshot, or an xslt
transform.
Also, NAnt can now work (in the last few months) with in-memory build
documents.
I like this idea of adding functionality to VS.Net by replacing their
build facilities.
What I really want is the VS.Net IDE where the build was done by NAnt.
This way I could do anything I wanted.
That may cost 3K to know how to replace the built in build commands. It
may be just as simple as
I'm sure that given enough time with the proper skill one could hack out the
hooks to the VS build system and menus. I *don't* have those skills BTW :)
But I think that and AddIn that would allow you to graphically configure
your build file and then execute it would be nice. (Haven't checked out
Title: VS.NET IDE Integration [WAS: New task idea]
I like this idea. It seems there is a ton of potential for increasing the NAnt user base if we create a seriously integrated IDE plug-in; one that does a lot of work for you.
I personally enjoy the control of writing the buildfile myself,
14 matches
Mail list logo
