Delivering value over tech obsession
Daniel, 28.06.2018
Let go of your habits, to become a value-generator
Daniel, 28.06.2018
Let go of your habits, to become a value-generator
Daniel, 09.10.2017
Get an overview of the basic tools and techniques involved in troubleshooting production issues with .NET-based applications.
Jeff, 10.03.2017
It is an exciting time to be a Sitecore developer these days now that Habitat and Helix are out to fill in what we all felt was missing from Sitecore all those years: patterns and standards.
Markus, 02.03.2017
The Sitecore Helix design principles exist for more than a year now and have caused quite some excitement in the Sitecore developer community. Here is a brief introduction of the principles, in case you are still missing out on it.
Andreas, 02.09.2016
We demonstrate an easy setup that allows anyone to send commands to your Internet of Things (IoT) device and get feedback. Our device of choice is Particle's Internet Button and we use an Android phone as SMS gateway. IFTTT's simple if-this-then-that recipes connect the Internet Button and the gateway phone.
Jeff, 15.04.2016
Building client-side web apps is the new trend, which means a lot of XHR requests to the back-end. Luckily, Sitecore provides a highly configurable Item Web API to help you with querying items from the client-side. But if you want results that are bound to your models and end-points not containing your query, then you will resort to querying items against the context database using ASP.Net Web API... only that... it doesn't work out of the box.
Jeff, 10.12.2015
Mocking Sitecore has been a tough nut to crack since Sitecore lacks the necessary interfaces that common mocking frameworks need, which really screws up automated testing for a lot of us. For that we turn to isolation frameworks like TypeMock and Justmock which unfortunately come with a huge price tag.
Jeff, 19.11.2015
With Visual Studio's publish functionality you can conveniently preview how your web project behaves and looks like on your local IIS web server. With that said, I believe publishing makes sense only if you've done significant changes since, depending on how big your project is, it may take some time to sync your deployable project files with the web site root folder, and deploying new DLLs and config files will definitely restart your website and flush your caches. But what if you just did a tiny update and just wanted to sync the changed file(s)?