Issue/660

[bnordli]

BREAKING CHANGE (As discussed on multiple previous occasions.)

Turn assembly specification upside down: Clients must now specify which assemblies to be included, instead of which assemblies to be excluded.

PROS:

• This simplifies assembly specification a lot (as this PR itself is an example of), since clients have much better knowledge of what should be in the application than what should not be in the application
• Better control (avoid sudden initialization failures because of new dlls being unknowingly included)
• In many cases better performance, since the sets of dlls included is bounded, instead of unbounded.

CONS:

• Clients must remember to include new assemblies, but this will be discovered early.
• It is a breaking change, after all, but should fit in the 2.0.0 milestone.

Fixes #660