ScanEntryAssembly() seems to run twice if called in config

[brendanjerwin]

This:

      Runner.Configure(cfg => {
        cfg.ScanEntryAssembly();
        cfg.UseCallbackToInstantiateExports(ObjectFactory.GetInstance);
      }).Run(args);

Results in a runtime exception complaining that my single entry-point is defined twice. If I simply remove the call to ScanEntryAssembly then it all works just fine. I suspect it is running twice.

[jacebennett]

Oops. I think this is a regression. I wish there was some sort of mechanism or practice that would help me verify that stuff still works when I make changes... =o/

Here's what I'm thinking:
This was originally intended to be called after DoNotScan().... makes less sense now, and doesn't actually say what it's doing. I'll rename that method to DoNotScanEntryAssembly(), and change both to set a flag to be evaluated after the config phase is complete.