Referencing external components will throw notfoundexception about orchard HOT 5 CLOSED

@Jetski5822 commented:

There is a bigger problem to this really. If you dont reference the new project in orchard.web, you cant use that project. Am i right?

from orchard.

ErikPorter commented:

Correct, you have to reference the new project in Orchard.Web. That is the current design. It is temporary.

from orchard.

@bradmi commented:

This will be addressed when we implement the module packaging/installation behavior.

from orchard.

IanGrainger commented:

Sorry if I'm not helping, but using the 0.1 release, you can use a project without rerferencing it from orchard.web. If you follow the instructions here: http://geekswithblogs.net/michelotti/archive/2010/04/22/create-orchard-module-in-a-separate-project.aspx you don't need to add a reference from WebPI --> Orchard.Widget. For a while. After a while you start seeing this bug. Which you can workaround by adding a reference from Orchard.WebPI to Orchard.Widget.

It looks like there's been LOADS of fixes since the 0.1 release, I'm really anxious to try a newer version of Orchard, but when I get the default branch code out of the repository, I can't add a module by following the walkthrough. Can anyone give me any pointers on how to create a module with the later (or latest) code? That'd be super-awesome.

from orchard.

@bleroy closed and commented:

Fixed

from orchard.