6 Results for Popular TechnologyPowerShell
For some time now, I've wanted to eliminate gulp from the build and deploy workflow of Helix based solutions. The use of Node, NPM, and Gulp has never set well with me. Surely there has to be a way to achieve the same results with more Visual Studio native technologies.
When it came time to setup automated deployments with Octopus Deploy, at the time, I didn’t find much in the way of how others were configuring Octopus with Helix based solutions. I hope this post, and the previous post on automated builds (Part 1), can be a road map for you or provide a starting point for your CI setup journey.
When it came time to setup automated builds with TeamCity, at the time, I didn't find much in the way of how others were configuring TC with Helix based solutions. I hope this post, and the subsequent post on automated deployment (Part 2), can be a road map for you or provide a starting point for your CI setup journey.
In a production environment, content updates are done on a regular basis. However, other instances like Development and Testing get out of sync when it comes to content. Developers or Testers with no administrative access to production have to rely on administrators or other team members to get these updates in the respective lower environments. In this article, I will discuss one of the approaches which will help non-administrative users to overcome this scenario...
Sitecore Powershell gives the flexibility to run Powershell scripts from the Sitecore context. With this power we have the ability to extending Sitecore Powershell to create custom commandlet. Custom Commandlets give you the ability to call .Net code from Sitecore Powershell.