|
Could someone point me to a good getting started article? I’m having difficulty even before the build, with slingshot. I manually build 5 solution files of three teams. Each solution file is a master which references other child .sln files. In addition the projects reference a shared common directory tree. Where files are relative to where I place a buildfile, or where I call it from, or where the master .sln file is, or the child .sln files are can get confusing. The build file tends to think all files are in a flat directory structure. Here’s an example of a command line I use: slingshot -nant -sln \source\common\dataservices\dataservices.sln build.basedir=\source > c:\buildtools\builds\dataservices.build
My source directory looks like this but deeper: \<solution> ..\Common \3rdParty \Microsoft \NUnit \Log4NET \Dataservices \Events \Messaging ..\Project1 \SubprojectA \Client \UI \Interfaces \Server \SubprojectB ..\Project2 \SubprojectA \SubprojectB ..\Project3 \SubprojectA \SubprojectB
Just last week I didn’t even know what slingshot was. I’m running it from command line, but the docs reference commands in XML format. Any pointers for a beginner?
Bill
|
