ArgumentException during bootstrapping when there are no views about nancy HOT 6 CLOSED

Roy,

As I read your issue report I immediately get a sense for what is happening. I believe the issue to be in the new view convention code and should be easy to resolve. I will investigate and resolve during the day. Thank you!

from nancy.

Excellent! I'll keep watching the repo and let you know if the fix takes care of the problem I'm seeing. If you need more detailed diagnostics I can provide those as well, of course (if I know where to look :)).

from nancy.

Pushed out some fixes to the master repo. Please let me know if this resolved the issue you were seeing. Thanks you!

from nancy.

This fix solves the startup problems for the regular application, that's good.

The bad thing is, is that the unit testing project still doesn't resolve the modules properly (only the FakeNancyModule gets registered). I'm just using a simple bootstrapper derived from DefaultBootstrapper and I did override the RootPathProvider property because otherwise I get an ArgumentNullException in FileSystemViewLocationProvider.cs: line 43.

from nancy.

I've just spent some time getting a repro scenario up and running, and I couldn't get it to fail :)
So I think this issue can be closed, since the unit testing problems seem to be unrelated.

And, again, I can confirm that this commit DOES solve the startup problems. Thanks for the help!

from nancy.

I found why the module didn't get loaded properly in the tests. Apparently I need to add this to my bootstrapper:

AppDomainAssemblyTypeScanner.LoadAssemblies(@"MyAssemblies*.dll");

Any idea how I can avoid this?

from nancy.