Command Line broken on dev branch origin/1.x

Topics: Core
Nov 15, 2013 at 1:38 AM
I guess this happens when you live life on the bleeding edge, but when I tried to upgrade my modules with "the shift", Visual Studio was telling me it couldn't find assemblies/references for Orchard (or any Orchard modules).

I checked out a fresh version of Orchard on the dev branch and tried to create a new module via the Command Line, but it seems I couldn't do anything at all with the Command Line (threw errors every time; I think about Site Settings or something?).

Alas, I will have to wait before I can upgrade my modules at this stage :-/

Does anyone have any suggestions? Is this a known bug which is on Seb's to-do list, or should I submit it?
Coordinator
Nov 16, 2013 at 6:27 AM
If you can't find it in the issue tracker, please file it.