I solved this problem by making an xslt to convert the .csproj file into a file list, then use the <copy> task to copy the files.
The XLST is attached, and here's a simplified version of my nant task (not
tested):
<target name="publish">
<style style="path/to/proj2list.xslt"
out="includedFiles.txt"
in="projectfile.csproj"/>
<copy todir="/path/to/server">
<fileset basedir="/path/to/project">
<includesfile name="includedFiles.txt"/>
<include name="bin/*"/>
</fileset>
</copy>
</target>
So the <style> tag parses the .csproj, (and should work with other languages,
not just c#), creates a file that is a plain list of
the files marked as "Content" or "None" in the project file, then uses that in
the <fileset> tag as the list of files to copy.
I think that solves it. If I get ambitious I might package that up as a task
and send it to nant-contrib.
Thanks,
Ryan
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Selke, Anthony
Sent: Friday, May 13, 2005 5:37 PM
To: [EMAIL PROTECTED]; nant-users@lists.sourceforge.net
Subject: RE: [Nant-users] Handling "content" in a web project
I would second this request.
VS.NET has a "deploy website" (or some such) command that you give it
server and it will copy just the content files and dependencies from the
local machine to the server.
Granted, you don't want VS.NET on your build server, but if anyone knows
what this menu command actually does and how it does it, that may be
able to be replicated.
Tony
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ray Johnson
Sent: Friday, May 13, 2005 5:35 PM
To: nant-users@lists.sourceforge.net
Subject: [Nant-users] Handling "content" in a web project
Importance: Low
Is there a facility to look at a web project and "copy" the files marked
as "Content" to a given location? This is kind of a deployment of a web
project - but we need to deploy to an intermediate directory rather than
an IIS install.
We could, of course, copy file patterns. However, one thing we love
about the <solution> tag is that we can manage what gets built via the
IDE.
Likewise, we would like to manage what gets deployed via the IDE.
Otherwise, we might add a new content type or something and someone will
forget to update the nant script and we will miss deploying something
with the developer going "uh - it worked on my machine!" :)
Ray
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be
the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id281&op=ick
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
proj2list.xslt
Description: Binary data
