Lately, I’ve been trying to improve my Salesforce skills. It’s been getting pretty interesting, to the point where I’d like to dedicate a post to it. (Hardcore .NET/C# readers may want to skip this week!) There are bits of the Salesforce developer ecosystem which I love and a few bits that are a little janky. I think the most interesting thing for developers is “Salesforce DX”, which I’ll try to explain briefly.
I’ve recently blogged about how excited I am by the promise of Blazor. Well, I’ve built my first Blazor app and, having tried it, I’m no less excited. There are still plenty of rough edges (which I talk about below), but it fundamentally works. In this post, I’ll try to outline the pitfalls as best as I can, in the hope that others find it useful. Please don’t construe anything I write as a criticism of the Blazor team – what they’ve done is already game-changing.
In the past, I’ve blogged about using AppVeyor for Continuous Integration (CI), but up to now, I’ve been manually uploading NuGet packages to NuGet.org. In this post – the 10th in the ConTabs series – I explain the steps I took to automate the packaging and deployment of ConTabs to NuGet.org. Or, in other words, how I’m using AppVeyor for my Continuous Deployment.
Open source projects need contributors to stay healthy and develop. In this post, I want to discuss the methods I’ve tried (so far) to attract contributors to my open source project (ConTabs). I’ll describe what I’ve done, summarise what little data I have, and reflect on what it might tell us about open source contributors. And, in the middle of all that, I’ll indulge in a quick digression on the subject of project hygiene.
In a brief break from the ConTabs series, today I’d like to share my three favourite (free) ways to enhance Visual Studio. FiraCode and Solarized will make your code look great, as well as easier to read. Productivity Power Tools is an awesome collection of 15 extensions that each make Visual Studio that little bit better.
I’m hanging my head in shame right now. A part of me doesn’t want to have to write this blog post, but the lesson is too important not to share. When I published version 0.3 of ConTabs 4 days ago, a big chunk of a headline new feature didn’t work. Wanna see how I messed up? Read on…
It’s about to be a brand new year. As 2017 ticks over into 2018, it seems like a good time to look back and review what we’ve been up to. ConTabs only really got underway quite late in the year and it’s no way near finished, so let’s call this an interim review. Still, we can see where we are, how we got here, who we met along the way, and where we might go next.
Today’s post marks a bit of a leap into the unknown for me, as I explore using static analysis to improve my code with NDepend. I explain how it can be hard to know where to start, but also how valuable the insights can be. The actionable changes are demonstrated with commits from my development of ConTabs. Finally – in keeping with the expositionary style of this post – I close with some general observations (including an attempt to explain the difference between NDepend and ReSharper).
I ended my last post by throwing my hands up in despair because adding my .NET Standard project via NuGet triggered the download more than 40 irrelevant dependencies. In this short update, I’m going to explain how to get this working.