I wrote a proposal at phpmanager/phpmanager#1

If you like to join, let me know.

Hi,

Just upgraded from v1.2 on a server and now our build process is broken (The Windows PowerShell snap-in 'PHPManagerSnapin' is not installed on this computer.). I wondered if this functionality had been turned into a module, but apparently not.

Is using this application with PowerShell no longer possible?

Thanks,

Robin

Hi,

we are using PHP 7.2.7 with IIS/Windows Server 2016.

When using PHP Manager to switch PHP from debug into development mode, it adds the following line to php.ini:

track_errors = On

With php 7.2 this now generates a deprecation warning:

Deprecated: Directive 'track_errors' is deprecated in Unknown on line 0

See also http://php.net/manual/en/migration72.deprecated.php

PHP Manager should stop adding/setting track_errors when PHP 7.2 or newer is used.

PHPMGRSNF.SNK.pfx file is password protected and as such the project cannot be built.

The project files actually include post-build step that sets up delay-signing for the compiled files (in debug mode) but that seems to be made for the old version and no longer works.

However I would vote for the password simply be removed and the snk file being checked in GIT to simplify collaboration.

Installed .Net 4.5
Ran the phpmanagerv1.5.0
Get Error 1001. Filename: \?\C:\Windows\system32\inetsrv\config\administration.config
Error: The configuration section 'modules' cannot be read because it is missing a section declaration.

Running on Server 2008R2 IIS7

Not really a IIS kind of person so I have no idea if this is because the installer is looking for PHP somewhere that it's not, which it is in the C:\Program Files\PHP. If this is a .NET problem because there are 1500 versions of .NET so when you state that it works with 4.5 is that 4.5.1 or 4.5.2 ect ect..

Any light you can shed on this would be helpful.

Really appreciate your efforts on this. The two post-build events don't work out of the box. I disabled them and have built the installer, installs fine, though I think it has some permissions issues (not surprising).

This is not an issue - I don't really see any other channel to say thank you for finally taking up this project!

I can confirm it works Windows Server 2012 R2.