A problem that my team has been running into on-and-off since working with ASP.NET Core is having a local install of our node toolchain fighting with Visual Studio's built-in version of node. Luckily, my coworker discovered the source of the issue (thanks, Pete!).
As I get back into the swing of things, I just wanted to say this: Joy and I are extremely blessed to have so many amazing people in our lives.
Well, our family made the local newspaper… but not for reasons we'd prefer.
Alright, important update for everyone: earlier today I was using the elliptical machine when I felt a sudden, and major, increase in my heart rate. After ending my workout, I rested and decided to self-monitor and see how my heart rate would proceed.
Another #BrandonEpisode of the #msdevshow where we talk about working remotely and telecommuting in general.
If you haven't been paying attention to the "New Microsoft", you may have missed that a lot of their new code is ending up on places like Github. Included in that is the backbone of their new Visual Studio Team Services build and deploy services: tasks.
I finally had a chance to get our codebase to the release candidate of ASP.NET 5. Excited to have a supported release available and more-or-less production-ready! As usual, here are my personal release notes to my team on the upgrade process.
I join the awesome hosts of the MS Dev Show to discuss some of the announcements from Microsoft's Connect() 2015 conference. We touch on ASP.NET 5, Visual Studio Team Services, and Visual Studio Code.
I don't know why it took me so long to figure this out, but it's totally possible to deploy binaries from the DNU toolchain instead of source folders.
After deploying one of our ASP.NET DNX web applications to Azure, we were running into an exception.