Uncategorised

Whilst developing our new set of websites we have been using MSDeploy to package up the websites for deployment to test and production Azure accounts. These deployments were being triggered directly using Visual Studio. Now we know this is not best practice, you don’t want developers shipping to production from their development PCs, so I have been getting around to migrating these projects to Release Management. I wanted to minimise change, as we like MSDeploy, I just wanted to pass the extra parameters to allow a remote deployment as opposed to a local one using the built in WebDeploy component in Release Management...

I am speaking at PreEmptive’s event on Application Analytics in at Microsoft’s office in London on the 30th of September. There are various speakers from PreEmptive, Microsoft and Black Marble at this free event. There are still spaces available, just follow the link: Application Analytics with Visual Studio and PreEmptive Analytics for more details and registration.

Whilst developing a new Release Management pipeline I did hit a problem that a component that published MSDeploy packages to Azure started to fail. It had been working then suddenly I started seeing ‘communication with the deployer was lost during deployment’ messages as shown below. No errors were shown in any logs I could find, and no files appeared on the deployment target (you would expect the files/scripts to be deployed to appear on the machine running a RM Deployment client in the C:users[account]localtempRM folder structure)....

As part of our IT refresh we have decided to move this BlogEngine.NET server from a Hyper-V VM in our office to an Azure website. BlogEngine.NET is now a gallery item for Azure website, so a few clicks and your should be up and running. However, if you want to use SQL as opposed to XML as the datastore you need to do a bit more work. This process is well documented in the video ‘Set BlogEngine....

Using the process in my previous post you can get a TFS build to create the .CSCFG and .CSPKG files needed to publish a Cloud Service. However, you hit a problem if your solution contains more that one Cloud Service project; as opposed to a single cloud service project with multiple roles, which is not a problem. The method outlined in the previous post drops the two files into a Packages folder under the drops location....