I have written a very simple nuget package called Phalanger.Core

Contains:

• php4ts.dll
• php5ts.dll
• PhpNetCore.dll
• PhpNetClassLibrary.dll
• web.config.transform (merges with an existing web.config) file with some default settings for Phalanger
• install.ps1 and uninstall.ps1 (scripts to create/delete the necessary Bin, Bin\Extensions and Dynamic folders: the necessary modify permissions need to be set manually if using IIS; IIS-Express runs without modifications)
  

This is only a sample for a nuget package, but you get the idea. The package isn't published to nuget.org but you can install it from the local drive:

• Create a new "Web Site" or "Web Application Project"
• Open the Package Manager Console
• Install-Package Phalanger.Core -Source "<folder_to_nupkg_file>"

And here is a sample package called Phalanger.Sample

Hi Tobias,

This is very good idea. I'll give it a try.

Thank you very much

uploaded a slightly more elegant solution (cleaner web.config), by defining the phalanger configuration in a separate "phalanger.config" file.

Hi Tobias,

I had little time to check this out...It looks good, Nuget package is certainly must for Phalanger. I think we should make core packages like this:

• Phalanger.Core just without php4ts and php5ts, because that would also work well on Mono and we don't have to have configuration filled with native extensions config stuff here
• Phalanger.NativeExtensions that would include php4ts and php5ts together with the native extensions and config This would package would work only on Windows
• Phalanager.MySql - unfortunatelly connector from Oracle is GPL so we have to keep it separatly from the main package
• Phalanger.Sample
  

Btw. Nuget didn't transform my web.config file well. I mean it only added assemblies to <system.web><compilation debug="false" targetFramework="4.0"> <assemblies> and nothing else... I didn't check the web.config.transform file yet. and also I don't see the dlls in the bin folder, but I can see them in the package... I'll take a deeper look

That would be really cool!

Don't know why the web.config didnt' got transformed. Worked for me, but I've testet it only in very simple scenarios. That the dll don't get copied in the bin folder could be caused by the fact that they are installed to the GAC by the Phalanger installer (I'm not completely shure).

That the Phalanger Dlls have the same Version Number (3.0.0.0) since the first release of 3.0 and they get installed to the GAC don't play very well with Bin Deployment. This could be addressed by changing to a semantic versioning aproach.

There's a good reading about NuGet and Bin Deploy from the WCF Data Services Team: http://blogs.msdn.com/b/astoriateam/archive/2012/05/17/nuget-and-bin-deploy.aspx
And also the semantic versioning is tackled by the team: http://blogs.msdn.com/b/astoriateam/archive/2012/05/07/wcf-data-services-now-with-more-releases.aspx
Maybe Phalanger should also follow this way in the future?