Hi Bill, This is probably the best place to ask usage questions like the one that you posted. If I'm wrong please correct me (Gerry, Ian, Scott).
For the senario that you described, you could get away with only one feature, if you want. You will then need to define a directory element for each directory that you want on the target machine. The components will then map to the feature(s) and a specific directory. One thing that needs to be done with this task is to eliminate the requirement that the directory structure needs to exist and, rather, support paths via NAnt's <include> tags. Hope some of this helps Jim > Hi All, > > (ASIDE: This is really more of a user question, than a development > question, but there doesn't seem to be a NAntContrib Users list, is it > the project's preference to send usage here, or to Nant Users?) > > > I've been working through how to use the MSI/MSM Tasks this past week > (if I get time, I'll try to publish my notes) and from what I have > seen it appears that every single folder in the install tree has to > have a corresponding entry in the Directories element, the Features > element, *and* the Components element. Is this correct? > > If so, do I have to do this myself (e.g. either manually or via > generation) or is there a way to get the task to recurse the tree and > create them? > > My fear is that trying to use the msi task is going to be infeasible. > We are considering ditching the msi task, and going with Wise or some > other commercial tool, but I wanted to get confirmation from here > first that I am not missing something. > > Here's how our install looks: > > First, we have an install source tree that looks something like this: > > installSource\ > Company\ > Project\ > Version\ > src\ > files > AssemblyOne\ > csproj + other files > Source\ > files > SourceTests\ > files > AssemblyTwo\ > csproj + other files > Source > files > SourceTests > files > ... > AssemblyThirty\ > ... > doc > folderOne\ > files > folderTwo\ > files > ... > folderN > files > bin > (bunch of stuff, including the built assemblies) > > Tools\ > bin\ > (bunch of tools that don't have their own install > location) > InstalledTool\ > bin\ > stuff\ > ... > > We want to package this into feature-set like this: > All > Binaries (installs Company\Project\Version\bin\*) > Source (installs Company\Project\Version\src\**\*) > Docs (installs Company\Project\Version\src\**\*) > Tools (installs Tools\**\*) > > Furthermore Binaries requires running some third-party installs and > some GAC registration. > > Am I seeing this right: that we need Features, components and > Directories entries for each folder? > > Best, > Bill > > William E. Caputo > ThoughtWorks, Inc. > http://www.williamcaputo.com > -------- > idia ktesis, koine chresis > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's Free Linux Tutorials. Learn everything from the bash shell to > sys admin. Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > NAntContrib-Developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
