Perhaps there could be some clarification here.
The ClickToBuild.cmd in the source enlistment will correctly build the solution, and also delete any unneccessary dlls from the module directories. This produces a version that can be happily FTP'd to your web server (otherwise there could be hundreds of
megabytes of dlls in the various module projects, which will take forever to upload - I think these are produced if you do a normal build from VS).
However I think the "Package/Publish" system in VS/VWD will fail in this regard. You can select "All files in this project folder" in the Package/Publish options. But I believe VS will build the entire project and all modules and attempt to upload everything
- which will take hours on typical upload bandwidth. Also it will overwrite Settings.txt and Orchard.sdf in App_Data, both of which could be very problematic for publishing to a production server!
I read somewhere that the developer/deployment story is being improved for the coming release, is there any more information around on this?
At the moment my workflow for updating my hosted version is as follows;
- Create a "clean" source enlistment locally
- Use "ClickToBuild.cmd" to build for upload (in my case I have a dedi server so I can do this directly on the server and don't have to upload all those big .dlls!)
- Maintain a local source enlistment where I do development and testing
- Upload individual files when not much has changed - this is usually just css, templates, etc.
- If I've built or modified a module / theme, I use the command line packaging tool to build a .nupkg ... I can then install this to the server instance just like any other module.
This really isn't too bad for most purposes, although it'd be nice to have the Publish tool behave properly. It's also fairly complex multi-stage process to do any updates; package, log in to site, Dashboard > Modules, install module, select file, install,
confirm features, possibly then have to click update. Maybe the Packaging module could simply have a "package push" command that would push a module to a server (requiring admin username/password obviously)
Also I've just noticed in latest 1.1 there's no longer an upload/install module option - where has that gone? I downloaded the modules from Gallery that I use regularly, so it was pretty quick to set up a new instance... The dashboard gallery interface can
be quite slow! (Somewhat mitigated by the addition of paging but still...)