Packaging problem

Nov 12, 2010 at 12:11 AM

When I try to create a package using the command line, like this:

package create Tagged

Where 'Tagged' is the module name, I'm getting the error "Module "Tagged" does not exist in this Orchard installation."

Do I need to qualify the name more? Should it be the name given in Module.txt, or is it something else? My module doesn't have a DataMigration, but I don't think that should be affecting this.

Nov 12, 2010 at 8:32 AM

Figured it out.

It's the folder name. I'd renamed my module, but kept the folder name the same.

So, it should be:

package create <ModuleFolderName>

Should probably keep the module name and it's folder name the same though to keep things clear.

Coordinator
Nov 12, 2010 at 6:27 PM

You're right. Can you please file a bug?

Nov 13, 2010 at 5:49 PM

Done here.

Coordinator
Nov 13, 2010 at 6:12 PM

The technical name of a module is the folder and project name, which must match. The Name in module.txt is the Display Name.

Nov 14, 2010 at 1:42 PM

Ah, that also explains why my first attempt at packaging made an empty package when the project name was different than the folder name.

I guess that's what happens when you change your mind halfway through about what you're calling your module.

All working fine now.