So there are occasions when working with a third party services you need to be able to develop and test against various scenarios and respond differently based on the response from that service. Controlling the response can be a challenge sometimes with service being outside of your control.
Thankfully you can easily fake the response with tools like fiddler. Fiddler is an awesome tool and has been around forever and has always had a spot in my developer utility belt.
Continue readingSometimes you run into scenarios where you cannot reproduce a bug/issue locally and requires you to investigate the issue on actual server where your are experiencing the issue. Now as it is a higher environment you most likely don’t have the luxury or at least you shouldn’t have Visual studio running on this environment where you could easily debug.
Thankfully though with the right tools and access you can easily setup remote debugging and step through the code as if it were running on your local environment and hopefully shine some a light on the problem.
Continue readingOften while working on projects, a team member may ask you to share your local Sitecore instance with them. Or you might even want to expose your local site to an external service for performance testing/analysis. There is a handy dandy tool that makes this really easy, ngrok. Using secure tunnels ngrok exposes local sites behind NATs and firewalls to the public internet. By connecting to the ngrok cloud service which accepts traffic on a public address and relays that traffic through to the ngrok process running on your machine and then on to the local address you specify.
There are various plans available including a free plan which supports:
Neil Killen 