Thanks for the quick response (as always)! Firstly a couple of clarifications about what I'm doing:
1) For now I have the default ELMAH (i.e. core) to continue to be memory based - I think this probably makes sense due to the complexities of later moving to ELMAH.SqlServer... the <errorLog> entry will (AFAIK) get duplicated, which is not something
that ELMAH currently supports.
2) The ELMAH.SqlCompact package doesn't use EFCodeFirst.SQLServerCompact - instead it uses the Sql Compact provider that is about to be release in ELMAH 1.2 (currently in Beta right now).
Going back to your suggestions:
1) I don't think I'm ready to embark on the PS script just yet... I think I'll wait and see how the platform evolves and the solutions that others come up with for their packages! :O)
2) I understand about not automatically showing the readme.txt files - perhaps an alternative suggestion would be one such that package authors could have a flag such as <requiresUserConfiguration>true</requiresUserConfiguration>. The package
manager could then check this for all packages installed and display an appropriate message at that point e.g. One or more of the packages that you have installed requires further configuration. Please look for readme*.txt or look in your web.config/app.config
for further instructions. This could also be for filtering packages so that unexperienced developers could avoid anything that involves extra work!
3) I like the idea of a readme.txt in the "Content" directory... however, I think
readme_ELMAH.txt might be a better name as that convention would group all readme*.txt files together, rather than being fragmented across the root folder - maybe that's some guidance that the team should share on the official site??!