

It was also apparent that just getting PhpStorm going and properly configured was more complex.

It became immediately apparent that PhpStorm is the superior product with more capability and features than Rapid PHP. I downloaded both for their respective evaluation periods (generous in both cases) and experimented with them both. I am also somewhat concerned about the future of plug-ins - will they be maintained as long as the parent tool and will they always be compatible? Because using the tools would have made Visual Studio the central tool, I decided not to bother. I considered looking at the two major PHP plug-ins for Visual Studio, VS.PHP and PHP Tools for Visual Studio. I use NotePad++ every day for general text editing and thus know it well but rejected it because of the lack of project management. I quickly rejected VSC and Atom because their project management capabilities did not jive with EW (or they didn't have project management at all). Visual Studio products do that but EW does not. EW has this but because EW is no longer maintained, its IntelliSense is not up to date with the latest versions of PHP and it is missing things from other languages as well. The equivalent of Microsoft's IntelliSense for the languages I most often use - PHP, HTML, CSS, and JavaScript.Have the editor/IDE understand the context or scope of a project.The ability to launch the editor from within EW.The features I wanted in a tool fall into two main categories - project management and editing. EW5 promised more support for PHP that was never delivered after Microsoft dropped EW as a product. My first priority is having a much better editor for PHP. EW has some excellent features, particularly in project management and including a couple of things I'd like to continue to use. I am not switching all my development activity away from EW and to a new editor. It is important to understand my perspective.

In this follow on article, I explain why I decided to purchase and use Rapid PHP 2016 by Blumentals Software. In my article " Why I Continue to Use Expression Web," I explain why Expression Web (EW) will continue to be my central tool for Web development projects and why I need something better for writing PHP code.
