The ultimate vision of the project is to remove the pain and friction
involved with creating a new project by automated the creation process
with templates.
The following is a sampling of potential usage:
rake newproject "ProjectName" --base-folder:c:\code
--use-template:fubu_and_structuremap_and_nhibernate.yaml
rake newproject "ProjectName" --base-folder:c:\code
--use-template:http://somecoolsite.com/fubu-getting-started.zip
rake newproject fubu-getting-started -name:"ProjectName"
--base-folder:c:\code
Given the task-based nature of the application, leveraging popular
tools like Rake and Albacore is certainly a strategic decision for the
project but should not get in the way of this discussion.
As I see it (from the examples given above), we've all expressed the
need to be able:
1) Output a directory structure
2) Output reference/redistributable assemblies in a common location
3) Create a solution file (05, 08, 10, etc.)
4) Create projects and add them to the solution
I imagined myself using in a way where I could create a template and
then defer the selection of assemblies to a separate service/task;
Chad's suggestion of using a zip file would do exactly that.
My next steps are to dig through Albacore a little and find the common
elements and work with Derick to see what we can do to reuse them.
Based off of what I've seen of Rake and Albacore, it sounds like the
ideal direction to go if nobody has any objections.
Derick, I'd love to chat with you about Albacore in general around
that time. I'll shoot you a line to see if you mind me picking your
brain for a little while :).
Chad, I'd like to keep you in the loop to see if it's something that
Fubu can use (and if somebody hasn't done it already, ha). And if so,
make sure that the end result can support what you need.
Derick, I'd love to chat with you about Albacore in general around
that time. I'll shoot you a line to see if you mind me picking your
brain for a little while :).