Closed robgha01 closed 4 years ago
@robgha01 I think you might be misdiagnosing the root cause here. Looks to me like you're getting an exception in the constructor function of whatever ServiceRegistry you're finding rather than any kind of problem with type scanning itself.
I'm closing this one due to a lack of activity, and I don't think it's actually related to Lamar.
The exception message thrown when "0" assemblies is found is "The data argument contains no data. Parameter Name: tasks" this dont say mush and need to get improved ex "Lamar could not find any assemblies matching ..." or just check if there is any assemblies and dont throw at all ?
The registration:
The throwing code: Lamar.Scanning.TypeRepository:61
Edit: What would be nice behavior is having a error message that shows from what ServiceRegistry this is from this way it will be faster to locate a problem.