7
Vote

Extension loader should look under any folder called *.Modules

description

This would enable single-repositories for a set of extensions on local clones, for example MyCompany.Modules.

comments

BrandonJoyce wrote Sep 13, 2012 at 4:18 AM

Unless someone beats me to it, I'm happy to implement this. Bertrand suggests looking into the CoreExtensionLoader. We will need to consider the build target that copies files from the modules folder.

BertrandLeRoy wrote Sep 13, 2012 at 7:06 PM

It would be great. Thanks in advance...

tmakaro wrote Sep 14, 2012 at 5:24 PM

So I am a newbie to Orchard but I did some hacking on this and was able to add Modules.CompanyA and Modules.CompanyB by hard coding them into the following 2 classes:

OrchardStarter.cs
RazorViewEngineProvider.cs

Its just a hack as there are no wildcards to search for 'Modules.*'

Oh ya, I used 'Modules.' instead of '.Modules' so that when I do a directory listing in windows explorer, they all group together when sorted by name.

BrandonJoyce wrote Sep 14, 2012 at 6:47 PM

Cool. My goal is to spend some time on this over the weekend. Maybe we can make the convention configurable too so people who like Modules.* better can go with that. Will keep you updated.

BertrandLeRoy wrote Sep 14, 2012 at 8:56 PM

Let's just support both.

BrandonJoyce wrote Sep 15, 2012 at 1:11 AM

Ya, that sounds good.

BrandonJoyce wrote Sep 19, 2012 at 1:31 AM

Orchard.Codegeneration will probably need an optional argument added for folder name. I'll probably go with orchard> codegen Module ModuleName /folder:Modules.YourModules

Probably just going to throw an error if the folder name is not in the format Modules. or .Modules. Alternatively, I could just automatically append .Modules, but I don't know if I like that.

BertrandLeRoy wrote Sep 19, 2012 at 2:15 AM

Good point. Should be fairly easy to add.