Closed andrewconnell closed 8 years ago
Try #1: Create a post deployment script This would use the existing deployment scripts, but do some post deployment cleanup and copying after all code has been moved.
Create a post-deployment.cmd
that simply echo's to the console a random message. Try to run this by adding POST_DEPLOYMENT_ACTION
app setting to the website pointing to the command as shown in this stackoverflow post
If that message shows up, then update the command:
Fixed... had to add a custom script so my post deployment script would be called.
Since the deployment model I'm using pulls the
settings.txt
from blob store, my deployment is setup (in\config\host.config
) to use the logic inOrchard.Azure.dll
to pull settings from an Azure blob, using the connection string setting in the web app's app-settings.However this DLL and another dependent one, are nested in the
\bin
of the Orchard.Azure module. Therefore whenever upgrading the Orchard version, I have to remember to manually XCOPY these DLLs from\Modules\Orchard.Azure\bin
to\bin
What I want to do is setup a deployment command script that will do this automatically as part of a post-deployment step so I can remove these DLLs from the
\bin
in the repo. See this post for details on how to create customdeploy.cmd
and set the project path.