The typical behavior for deployment is to copy your changes from the local machine to the remote server. But sometimes, you want to do more than what the deployment feature does for you. This is why VS.Php comes with the website copy feature. This is a drag-n-drop interface that lets you copy files from and to the remote server. It also lets you create, delete and rename folders on the remote server.

VS.Php ships with the latest Zend Framework and it is pre-configured to work with the built-in preview engine out of the box. This means you can start referencing the ZF classes from your project and VS.Php will be able to find those classes and provide intellisense support. Also, when you debug your application using the built-in preview engine, the ZF will be loaded and the application will execute correctly.

VS.Php allows you to create PhpDoc skeleton comments based on class, method or function definition. The editor uses the information in the code to prefill the PhpDoc comment. To use this feature you can do it one of two ways. First you can right click on the function, class or method and select: Insert Comment. The second option is by typing /** in the line above the function, class or method.

In VS.Php you can select which Php modules are available in intellisense. The list of Php modules is available in the Php Modules node in the solution view under the project node. VS.Php already have a few modules added by default that are not listed in the list like mysql and a few other core modules in Php.

VS.Php does not include all Php modules in intellisense to improve the responsiveness of the editor and facilitate finding the function you are looking for.

If you are having issues with the deployment component or remote projects feature you can enable tracing to help diagnose the problem.

Go to the VS.Php main registry hive:

HKEY_LOCAL_MACHINE\SOFTWARE\Jcx.Software\VS.Php\V2.4\2008

Add the following entries:

DeployTrace = True
DeployLevel = All

Please note that the 2008 must be replace to SE, 2005 or 2003 if you are using those respective editions.

VS.Php allows you to deploy files to a remote location. To deploy your project, right click on the project in the solution view and click deploy. Also when starting a debug session, VS.Php will automatically deploy your project. VS.Php will only deploy the files that are newer than the ones on the server.

• Network share
• Ftp
• SFtp (SSH)
• Ftp/S (SSL)

Deploy single files

You can select a file from the solution view and deploy it. This is useful when debugging, it allows to push new changes to the remote server without interrupting the debug session.

Pre and post deploy command

Sometimes you want to execute a script before and/or after deploying your project. Use these settings to enter the name of the script (batch file) or process you want to execute.

Main updates in VS.Php 2.3

• VS.Php SE and 2005 support Windows Vista
• Support for Visual Studio 2005 SP1 and Visual Studio .Net 2003 SP1
• Support for remote server projects. Edit remote files as if they were local.
• Support for importing projects via Ftp, FtpS and SFtp
• Add support for Ftp over SSL
• Smarter deployment mechanism
• Improvements in auto formating
• Latest Php 5.2 and Php 4.4
• Updated Php and PEAR documentation

Major Changes

• New project types including command line projects, php version specific projects and Zend Framework MVC projects.
• Zend Framework integration
• PhpDoc automatic comment generation with smart editor
• Improved website copy
• Variable color coding inside strings
• Improvements to class autoloader
• Man

When VS.Php receices notification that a breakpoint has been tiggered on the server, it gets the remote file name in which the breakpoint occured. It then needs to find a local copy of that file to show the developer. In the local system, the phpproj file has to be at the root of the application. Any breakpoints that occur on files outside this folder will not work.

For example, let's say you have an application on the remote server like this: