The other day a new version of the ‘pre-alpha’ client framework Aurelia was released. It was accompanied by a blog post at Durandal.io. It contained a section titled “How to Update” that described the steps to update your current Aurelia app to the current version. The update steps all work great but
When working in Visual Studios it sometimes becomes required to open the command line in your current folder structure. While it’s possible to Window + X choose command prompt and cd your way to your current project; wouldn’t it just be easier if you could get there straight from Visual Studio?
Things are changing on the web in the Microsoft world. ASP.NET 5 uses a different approach to static files than previous iterations. While before the root of your project was the root of your website that is now not the case. Which Root is Root In this post we will walk through
The Ladies, Gents and Paperclips at Microsoft are taking the easy road with some aspects of the web development tool chain this go around. Instead of reinventing the wheel that the rest of the web development community is already taking around the block they are just including some of those preexisting tools.
I’ve been trying out Visual Studio 2015 CTP (Community Technology Preview 5 for those of you who are curious to know what CTP means but not curious enough to look it up) for a while now and I was having an issue with using gulp from the task runner explorer. In CTP
The other day at work I started working on a project that had made heavy use of a jQuery plugin for masking date inputs. I was re-implementing some things with Angular and had to maintain the same behavior that the users had come to expect as the norm. There were strange issues