Typical of most developers, the documentation comes after the development.

I want to hand over the MSI development over to someone else but obviuosly not just show them the project file and say "get on with it!"

In your opinion, what would be the best way to document this information?, flowcharts are normally good but with having 50 odd custom actions runnning under various conditions could prove to be a nightmare to write.

Also, apart from the obvious Microsoft office suite are there any CASE tools or alike which could handle this well?


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I use a standard for creating custom actions.

By prefixing properties, CA's, File / Reg variables you can use code to parse the MSI and extract anything that matches the prefix. This way you can automate the creation of tables containing the customised sections of your app.

I use the MS Office object models to generate doco. (ie Word.application) I can send some sample document templates that show how to setup a document to receive data pushed in from external sources.
Answered 09/20/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment

If you could send me those templates as well I would much appreciate it! Thanks in advance.

Answered 09/21/2007 by: danr29
Purple Belt

Please log in to comment
I'd appreciate it if I could have a look at those templates, John ..

This discussion is interesting as I'm working with developing better docu standards myself at the moment. We use a similar approach but as we don't like MS Word we output the data to a plone site instead :-) This far it seems we got quite a job to do when it comes to cleaning up stuff we did BEFORE setting the standards (I know, thats not the way it should have been, hehe).

One thing worth mentioning is that we are now considering moving from using setacl.exe to setacl.ocx and custom tables, like documented here by a post from nheim. The extra tables kind of makes the ACLs more self-documenting, I feel.

Edit: nheim credited for the link
Answered 10/09/2007 by: deploy.no
Orange Belt

Please log in to comment
send me your emails and I will forward the doco. [email=john.mcfadyen@gmail.com]john.mcfadyen@gmail.com[/email]
Answered 10/10/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment