Generation for multiple assemblies

[Alex McMahon]

Just used docu for the first time against one of my assemblies and it
looks pretty cool, but about a million times easier to use than
SandCastle! Anyway, my first query was how to run docu against
multiple assemblies;

Admittedly while writing this I figured it out (you just pass each
assembly as an argument e.g. 'docu myassembly1.dll myassembly2.dll -
or at least this works for 2!).

I also couldn't find any command line help. If there is some perhaps
this could be pointed to in the 'Invalid argument' message.

Is there a way to specify a lot of assemblies? I guess a build script
could be made to call the command line and automatically put in all
the output dlls; but might it be better to allow for wildcard matching
or something?

[James Gregory]

Hey Alex,

Glad you like it so far :)

Currently the only way to handle multiple dlls is to pass them one-by-one as arguments like you have done.

Admittedly I've focussed more on the architecture than anything and as such the console app isn't as user friendly as it should be. I believe if you call it without any params it'll show you the syntax, but there's little more to it than what you already know.

I've created a couple of new tickets based on your feedback: firstly one for wildcards in dll names and then one for making the command-line help better, I'll hopefully be able to get to these soon.

Thanks,

James

[James Gregory]

Hey Alex,

Just to let you know that I've committed a change that adds wildcard matching to filenames. It's nothing particularly clever, it just uses the Directory.GetFiles pattern matching capabilities that're described in the remarks section on this msdn page.

It allows you to do things like: docu MyProject*.dll to match any dlls starting with MyProject.

I've not yet pushed this change into a release, so you'll either need to hang on for that or build from source (if you're not already).

James