I would like to get it into the NAnt CVS repository, but I would at least like it to be using the NAnt <csc> task. If you (or anyone else for that matter) would like to get a crack at the code before I've finished cleaning it up, I could send you a raw code snapshot and just manually merge your changes into my local copy as you make them. I'm sure that as different language projects get added, more refactoring will be needed to reduce the code sharing.
The biggest showstopper for me right now is that the <csc> task doesn't support all of the arguments that I need to pass to it. It's not a huge issue, mostly just one of finding time to list and implement these arguments. I think the VB task has a greater number of arguments implemented, so you might not have a problem.
I may also have to check that the <copy> task is able to overwrite existing files with the "read-only" attribute. It's amazing how many times this comes up in a compile from CVS (or any other source-control system).
Let me know if you want a copy of the source.
Brant Carter wrote:
Are you planning on releasing the source any time soon? Does this work with VB.NET projects? If not I would be willing to put in the time to do the conversion.
b
From: Matthew Mastracci <[EMAIL PROTECTED]> To: Brian Deacon <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: [nant-dev] Visual Studio solution builder Date: Sat, 22 Feb 2003 09:30:32 -0700
Nope. It can (and does currently) build ASP.NET projects for myself. As long as you point it at the .csproj file on the disk itself, it won't freak out. You can event just point it at your entire source tree and ask it to build all the projects. It will build them all in the proper order, including your web projects, and leave the .dll files in the proper bin directories for whatever method you use to deploy.
Brian Deacon wrote:
Bravo! I'd love to see the code once you've got it dressed up for date night. :)
Sounds like this also won't freak out trying to build an ASP.Net sln in the absence of the web server?
Brian
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Mastracci Sent: Saturday, February 22, 2003 8:02 AM Cc: [EMAIL PROTECTED] Subject: [nant-dev] Visual Studio solution builder
Now that NAnt 0.8.01 has been released, I've decided to release the latest version of my Visual Studio project/solution builder. This version has been enhanced in a number of ways:
- It now uses some internal NAnt tasks to perform its actions (License and .resx compiling). When I have a chance, I'll fix it to only use NAnt tasks to do its magic.
- It can handle building a solution, even one that uses Enterprise Template Projects.
- It will automatically resolve extra dependencies in solutions if the projects are built at the same time.
- If the solution is built by referencing the output file of the projects (versus referencing the project itself), it will automatically detect this and treat it as a reference to the project itself (including
matching the solution's build configuration).
To use this task: - Unzip the task dll into the NAnt 0.8.01 directory. - Run NAnt using a .build file that has a <solution> task (see below)
If you have any issues, please email myself ASAP and I can try to resolve them. I will be trying to get the source available soon as well. It *really* needs to be cleaned up, but it can at least be patched by others if I put it into CVS.
*** Please note that this has not been tested with VS2003 solutions. As
far as I know the project formats are similar, but I can't guarantee it will support every nuance (especially custom build steps).
Here is an example build file:
<?xml version="1.0" ?>
<project name="nant" default="x"
xmlnds="http://tempuri.org/nant-vs.xsd";>
<target name="x" description="Perform a 'debug' build">
<!-- Build the solution "main.sln", release configuration -->
<solution solutionfile="main.sln" configuration="release">
</solution>
<!-- Build all of the projects under the projects/ directory, automatically resolving dependencies, use the release configuration for each -->
<solution configuration="release">
<projects>
<includes name="projects\**\*.csproj"/>
</projects>
</solution>
</target>
</project>
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
