I have often had the glorious opportunity to watch someone try to deploy a project by picking compiled libraries that they had thought had changed. \u00a0Every time they deployed by using this method, their live project would not run. \u00a0When they run their project on the development machine, it runs no problem. \u00a0This confuses the developer to no end resulting in a multitude of profanities.<\/p>\n
This is a bit painful to watch. \u00a0 I really do not understand why developers do not deploy by using installation packages or deployment methods provided by their development environment. <\/p>\n
Today, I had offered to deploy the project for them and used the VisualStudio deployment utility. \u00a0This was a web-based project so it was very easy. \u00a0The deployment wizard walks you through the process starting at where you would like to deploy to. \u00a0The deployment results in only deploying the files necessary to run the program or website. \u00a0I had learned this principal while working for a London company; ICINITI. <\/p>\n
ICINITI would use a packaging tool to deploy products to customer machines including websites. \u00a0Their projects would often automate part of the process including site setup, run batch files and deploy other required files. \u00a0Deployment to customer’s computer systems would go pretty quick. \u00a0Sometimes it was so smooth the customer was able to conduct the deployments themselves.<\/p>\n
Today’s deployment took about 5 minutes or less. \u00a0 I had later demonstrated how and what I had done. \u00a0 I believe this will be used a little more often as a deployment technique.<\/p>\n