We pleased to announce the release of VS.Php 2.7 for Visual Studio 2008 and
Visual Studio 2005. This release introduces a number of new key features and
enhacements of existing features.
Silverlight
One of the most exciting new features is Silverlight integration. With VS.Php
2.7, you can develop Silverlight applications and host them in your server
side PHP application. VS.Php makes it easy to develop, debug and deploy these
types of applications.
read more
... (more)
I have fixed a bunch of issues on 2.7 so I've decided to make it available to
all.
Here is the list of fixes:
Improved project-wide intellisense Address some of the XDebug crashes in
Apache. Only allow one thread at a time to avoid concurrency issues in
XDebug/PHP Improve PhpDoc intellisense, protect better against invalid
expressions for evaluation Allow to create IIS project on root di... (more)
Now that VS.Php 2.7 is out, I'll like to share our progress with VS.Php for
Visual Studio 2010.
If you are currently participating on the VS2010 beta program, you can try
VS.Php for Visual Studio 2010.
Here is a screenshot of VS.Php running on Visual Studio 2010:
There are a number of things broken but basic functionality is there.
You can download the latest build here: vsphp_en_2010.exe... (more)
I have made some improvements to the smart indentation feature in VS.Php.
Smart indentation can be enabled here:
I tried to address a number of issues with the previous version where things
didn't align well. In many cases things don't align well if there are syntax
errors so it is difficult to do it then.
One of the things I do as I write code is Ctrl+K Ctrl+D, this will auto
indent th... (more)
In the past few days there was a change in Vista (I'm guessing) in which
localhost resolves to the IPv6 loopback address instead of the IPv4 address.
The problem is that VS.Php's apache server only supports IPv4 and therefore
when you start your debug session you get an error saying the page can not be
displayed.
I uploaded a new version of VS.Php that explicitly uses 127.0.0.1 instead of... (more)