Home > Article > Backend Development > How to set up graphics and text in php using Visual Studio_PHP tutorial
现在,三层、mvc之类的思想遍地开花,使得代码和html得以分离,加之随着开发的分工和项目的增大,一个好的IDE能为编码工作提供了许多的便利。就像开发java用eclipse,.NET用visual studio一样,开发PHP也很需要一种这样的利器。常见的php的IDE有Eclipse,NetBeans,Zend studio,vs.php等。这几个我也都用过,其中Eclipse,NetBeans,Zend studio都有win和linux的版本,也都集成了像代码感知、调试、设计、片段等的功能,都用过一阵子后发现,在windows下,个人感觉还是vsiual studio+vs.php最是好使。主要的原因就是速度。 vs的速度真的是快其他的IDE太多了,无论是从启动速度还是使用过程中资源的耗用都要好于其他3款,毕竟是微软自家的东西。
vs.php以插件形式安装到vs,现在已经出到2.9,支持visual studio2005~2010,到官网下载安装即可。默认是30天试用,可以搭配visualstudio express。安装以后,在visual studio的新建项目里就会多出来php的项目。
当然也支持一个解决方案,多个项目。
vs.php在启动的时候,会自动扫描包含在项目里的php文件,并加载到代码自动感知里。同时,未避免加载太多的感知支持,默认并没有加载不常用的php扩展的感知支持,如果有需要的话,可以右键项目,选择Add Php Module, 在列表里选择要添加的扩展,如图。 如果要对项目外的文件添加感知,也可以通过右键项目,选择Add Php Refence,选择文件添加支持。
需要调试的话,可以编辑项目属性,这里的话,有个不太好的地方就是Start page一定要设置,不然无法启动调试,而且按F5运行调试时,就是打开这个起始页,没办法像ASP.NET那样,运行当前打开的页面。
你可以根据需要选择调试的模式等配置,当然,如果你觉得有的东西老改麻烦的话,也可以通过修改vs.php的配置来一劳永逸。vs.php内带了一个apache2.2在安装目录下,所以,选择调试的时候,你可以决定用内置的apache还是服务器的apache,同时,安装目录下有PHP4,PHP5的目录,里面的东西也可以修改使用,诸如php.ini。如果使用xdebug来调试的话,推荐修改下php5下的php-xdebug.ini,添加修改下
[XDebug]
xdebug.idekey = vsphp
xdebug.auto_trace=On
xdebug.collect_params=On
xdebug.collect_return=On
xdebug.trace_output_dir="d:/x-debuginfo"
xdebug.profiler_enable=On ;打开效能监测器
xdebug.profiler_output_dir="d:/x-debuginfo"
xdebug.default_enable = On
xdebug.show_mem_delta=On
这样,调试时就会输出调试信息到d:/x-debuginfo,再使用WinCacheGrind来查看这个执行的CPU,内存使用情况,函数执行时间,尤其方便进行性能优化。如
Language Reference目录下存放的是php的函数注解,智能感知就依赖这些文件,修改里面的注释信息,就可以改变感知时的提示,现在是全英文的,不知道会不会出一个中文的注释,期待。
In terms of code intelligence, vs.php can only score 80 points. Sometimes it is quite depressing to not be able to get it out. Of course, this may be related to the fact that you distribute classes or functions in other files. vs.php will automatically parse the include statements of require, include, etc., and try to load and parse this file. When using the instantiated object, in the current When there is insufficient information, it will try to load the file according to the settings in the project configuration properties
Just like __autoload in php.
In addition, standardized and reasonable comments will provide great convenience for code-aware prompts, especially for customized class objects. For example,
The $this->response here does not know what type it is, so there will be no prompt. However, if the type declaration @var type is added, the member information of the object can be displayed normally. Tips etc
In terms of breakpoint debugging, although it is sometimes impossible to capture breakpoints, it can still be achieved.
In fact, many times, because this function is not reliable enough, in this case I still tend to output the variables myself to check.
In general, I personally prefer vs.php. Compared with the running speed and resource usage of zendstudio, NetBeans, etc., this is undoubtedly a better choice. Moreover, I personally like to use ASP.NET pages with smarty syntax as PHP templates. Compared with pure HTML templates, .NET pages have incomparable advantages in visual studio, such as Masterpage and usercontroller, both can be displayed normally. , this is quite convenient for control reuse and design. The specific template classes will be sorted out and released when I have time.
If you are still using Notepad, Dreamweaver or the like, you might as well try vs.