>>qwertie: So you thought it was better that users copy-paste the same documentation manually to each overload?
Inherit what is common, (in this case the summary, remarks, parameter:destination), and then provide the difference.
In reality, each overloaded method does something special; providing default value for "missing" parameters for instance,
and there is no way this can be automated. The countDown in your sample could mean there is a startTime; may be the
time of calling the LaunchShuttle or there is a delay time after calling the LaunchShuttle. So the point is do you really
want to provide the user with a useful documentation or anything goes?
>>qwertie: Am I the only one that thinks documenting each one independently is a waste of programmer time...
That you do not want to use even the inheritdoc, as in your first post is what look strange.
>>qwertie: Are you suggesting each user should separately write their own VS macro or add-in...
No, since personally I do not see the need for this, and it is not like every method in a every class is overloaded.
Adding inheritdoc is not a work I will wish to automate.
The point here is, the commenting part of the documentation process is done in the VS, and this is where you
automate if needed.
>>qwertie: Even if more than 1 in 20 developers knew how, don't forget, we don't all have VS Professional Edition.
Is not like a facility is not provided. And already, VS adds the template if you type ///, and you never have to type
a parameter list as you claimed in your earlier post.
Only the Express edition meant for hobbyists and students does not support macros and addins.
There is more work still needed in the Sandcastle, that is why in my first post, I still went ahead and showed you
where to start, if you think this is a useful feature that deserves time and resources, then please contribute this to