This project is read-only.

How to handle install/uninstall of module(s) while using a TFS build

Topics: General
Dec 1, 2014 at 9:53 AM
I am working on creating automated build for a Orchard based web application. Currently our team is using packages (createdted through Orchard with file extension .nupkg) to install a specific module. But in case of using the TFS build the web application will be published as a whole. The requirement is to have a TFS build, but at the same we are looking for the flexibility Orchard is providing to install module(s) independently.
Kindly provide information, on how to handle individual modules when using TFS build for the whole web application.

Example: If in a build the changes are made into two modules (Login and Reports). Same build is deployed to test server, while testing it is found that Report module is having some issue and is not working as expected. Now as the application build was used instead of individual package file, how changes for Report module can be reverted, without effecting the changes done for Login module.
Dec 10, 2014 at 2:31 AM
You can remove modules by simply removing its folder. There will be some leftover data, but that should be inactive if the module is gone. And in any case, I imagine that you're only installing unproven modules on dev machines that can be reset easily with a fresh database?