I'm in the process of migrating a project to the wonderful Octopus Deploy from MSDeploy. But I hit a weird hiccup where Octopack was adding some strange extra files into the bin folder of my web package: [CreateOctoPackPackage] OctoPack: Added file: bin\packages\structuremap.3.0.3.116\lib\net40\StructureMap.pdb [CreateOctoPackPackage] OctoPack: Added file: bin\packages\structuremap.3.0.3.116\lib\net40\StructureMap.Net4.pdb [CreateOctoPackPackage] OctoPack: Added file: bin\packages\structuremap.web.3.0.0.108\lib\net40\StructureMap.Web.pdb See how the files are within subfolders of the bin folder? Very strange. So it turns out I was running the MSDeploy and Octopack processes in the same MSBuild: /p:DeployOnBuild=True /p:DeployTarget=Package…
I saw this tweet from @JamesNK: https://t.co/xLKX93tpbo was released 10 years ago today. Here is 10 years in 3 1/2 minutes https://t.co/6vLokHIQAN— James Newton-King ♔ (@JamesNK) June 27, 2016 What an awesome way to visualise changes to your repo! James made it using an open-source product called gource. I haven't played with it directly yet, but I found a plug-in for Visual Studio to allow you to visualise TFS Source Control using gource. And there went 10 minutes of today, watching the repo at my work grow. A few projects back I was using hg -churn to see the workload of different members of my team, but this is definitely a much cooler…
Azure PowerShell 1.4.0 breaks old Azure Resource Group projects
By: Anthony Meehan on
I'm working from home tonight on a new machine, so I've installed the latest Azure SDK and Azure PowerShell (1.4.0). Our existing Azure Resource Group project failed to deploy to my Azure environment using the Visual Studio deploy prorocess: The property 'Key1' cannot be found on this object. Verify that the property exists. At ***\Scripts\Deploy-AzureResourceGroup.ps1:70 char:5 + $StorageAccountKey = (Get-AzureRmStorageAccountKey -ResourceGroup ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], PropertyNotFoundException + FullyQualifiedErrorId : PropertyNotFoundStrict The variable '$StorageAccountKey' cannot be retrieved because it has not been set. At ***\Scripts\Deploy-AzureResourceGroup.ps1:90 char:82 + ... irectory""", $ArtifactsLocation, "/DestKey:$StorageAccountKey", "/S", ... + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (StorageAccountKey:String) [], RuntimeException + FullyQualifiedErrorId : VariableIsUndefined The variable '$LASTEXITCODE' cannot be retrieved because it has not been set. At ***\Scripts\Deploy-AzureResourceGroup.ps1:91…
So it has been a long time between posts, but life has been pretty hectic. Work-wise I've been leading a large project (which has required a fair bit of overtime) so I haven't had much spare time. The project has however moved been dragged into a more continuous delivery model, and as a side-effect of the security system design we have built a simple feature toggle system. Not all bad then, as it has given me further ideas for FeatureVersioning. But more on that in a later post. cycle-with.me Today I wanted to get some ideas down for cycle-with.me. I went for ride with some friends for this first time in a while today. And it is usually…
A bit of googling for this blog post and... it turns out that there is plenty of history surrounding feature toggling already. In fact there is already an open-source .NET library FeatureToggle by Jason Roberts (who is also lives in Perth) which started back in 2012! What does that mean for my project? For one I'll need to come up with a new name, as Jason already has dibs on the NuGet package name (including >5,000 downloads!). Having a quick look at Jason's codebase it appears to be a sophisticated solution with plenty of extensibility points. So should I fork?. I know us software developers love to reinvent the wheel, but I do honestly think my thoughts around…