Jeremy Davis
Sitecore, C# and web development
A common but not-fun issue for working developers is when you do some work, test it locally, submit a PR and then find that it blows up on someone else's computer. I'm not too proud to admit that I had an issue with this recently, which highlights a thing you have to remember when working with Sitecore Content Serialisation.
I hit a rather confusing issue with a release a while back, which initially appeared to be a Unicorn problem. But after investigating the details, I think this was actually an infrastructure problem causing some odd behaviour. I doubt this is a common problem, but still worth writing down in case it's a challenge for anyone else...
Ever had a tool that works reliably suddenly not work? I had a problem like that recently, and it lead to some experimentation that I think I may need to come back to later. So this is mostly so I can remember what I was doing when I get back to this. But as we move toward a more "platform agnostic" with more use of .Net Core on Linux, maybe there's something here that might help you too...
My moment of confusion from a while back came in the middle of a big chunk of client development work. The solution already used the generator-helix package, but the work needed to make use of TDS, rather than Unicorn. Since I was going to be involved in creating a set of new features, and potentially a load of TDS projects, I wondered what it would take to make the generator-helix package support TDS...
Quick one today, as I need to spend time writing up my presentation from the Sitecore Technical User Group in Manchester last week. (Hopefully will have something done for next week's post)
