Using the SFTP extension for Visual Studio Code is essential for anyone wishing to maintain a Web site in a traditional manner, but despite development having moved into different hands, the tool is problematic.
The SFTP extension for Visual Studio Code is an extremely important one because VSC has no native publishing capability. SFTP has some problems and its future is uncertain.
Visual Studio Code is heavily dependent on extensions and the quality of those extensions is important. There have been some improvements, and I learn a couple of things.
With more projects in VSC's corral and many, many more hours behind the keyboard, a few cracks are beginning to show. Is PhpStorm in my future?
Expression Web keeps its metadata in a way that was practical two decades ago but is cumbersome now. It's not needed with Visual Studio Code. Here's how to deal with it.
Working with Visual Studio Code is a challenge but also a pleasure. Understanding it better is bearing fruit, one keyboard shortcut and one extension at a time.
After twenty years using FrontPage and then Expression Web to build Web sites, something new is needed. Can Visual Studio Code do the job?
Back on its two-year schedule, Blumentals releases its newest update to Rapid PHP, the PHP-centric version of its Web development tool suite. It is a modest release with some important improvements, but probably not enough for me.
Recent events have conspired to make Expression Web far less useful. The moment I've been dreading, completely changing my toolset, is nigh.
After my list of banjo makers had been around for a few years, I thought I might expand my listings to include other Bluegrass instruments. I started a guitar list. However, I'm not keeping that up well and want to focus on banjos, so the guitar list is being retired and I won't be doing other instruments as originally planned.