I\'ve got an solution which consists of Windows Services and websites. When upda

Question

I've got an solution which consists of Windows Services and websites. When updating the applications currently, the following steps are undertaken

Build of solution
Post build tasks copy the DLLs to a specific application folder
Build script is ran which gathers the DLLs relevant for each application (this is done via a text file containing a list of the DLLs per application, this needs to be changed if another DLL is added to the project). This is then stuffed in a release repository and pushed up to Github
Release repository is checked out on the server and a script is run to overwrite the DLLs and exes of both the Windows services and websites. All of this is done via XCopy along with some Windows service commands to Start/Stop services.
I was wondering how to make this a bit easier? Or whether someone in a similar scenario does it differently?

Explanation / Answer

Yes and no.

Yes because it would not be hard to fix the pain points in step 2 or 3 without much trouble -- just redo your packaging to call msbuild on individual projects with a desired output directory so you don't have to maintain the file lists at least.

Yes because you could probably dodge the whole github package by perhaps deploying your built artifiacts to the machine.

No because your deployment script is probably just about what you'd need for your one-off app and it is getting the job done and there might not be a better way to get there as most of the new toys are cloud-facing and windows services implies not cloud-facing.

You might also want to look at using something like teamcity or jenkins to orchestrate, record and otherwise manage the process.

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.