Hey Christian,

You probably need to fully qualify the assembly name to get it working.

Here's a non-working example; the assembly is loaded but object unwrapping doesn't give us an IDispatch'able handle, so instantiation fails.

Don't ask me how you determine the version and key tokens; I pulled these out of a decompiled .tlb file :-/

$f = new DOTNET('System.Windows.Forms,Version=1.0.5000.0,Culture=neutral,PublicKeyToken=b77a5c561934e089', 'System.Windows.Forms.Form');

PS: the next HEAD snapshot will contain better startup and error reporting for these things; possibly fixing that other  .net bug you reported a little while back.

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Description:
---------------
As far as I can tell this bug is still present in 5.2.6. Using a fully qualified assembly name reproduces a different error, so it might be a step closer to working. 


Reproduce code:
---------------
$object = new DOTNET( 'System,Version=2.0.0.0,Culture=neutral,PublicKeyToken=B77A5C561934E089', 'System.Diagnostics.Process' );


Expected result:
----------------
- no output --


Actual result:
---------------
PHP Fatal error:  Uncaught exception 'com_exception' with message 'Failed to instantiate .Net object [Unwrapped, QI for IDispatch] [0x80004002] No such interface supported
'

This bug is still present in PHP 5.3.8.

Here is the code I tried to use:

$sp = new DOTNET('System, Version=2.0.0.0, Culture=neutral, 
PublicKeyToken=b77a5c561934e089', 'System.IO.Ports.SerialPort');

The error message:

Fatal error: Uncaught exception 'com_exception' with message 'Failed to 
instantiate .Net object [Unwrapped, QI for IDispatch] [0x80004002] No such 
interface supported '

Reopening per the last two comments, although I suspect this is firmly in the 
"patches welcome" category.

Strange... the first works, the second gives that exception:

$fm = new DOTNET('System.Windows.Forms, Version=2.0.0.0, Culture=neutral, 
PublicKeyToken=b77a5c561934e089', 'System.Windows.Forms.Form');

$sp = new DOTNET('System, Version=2.0.0.0, Culture=neutral, 
PublicKeyToken=b77a5c561934e089', 'System.IO.Ports.SerialPort');

Both are with fully qualifie assembly name... 
Is there any way to activate more detailed debugging informations to see what is 
happening in background?

I think the problem here is that you can only instantiate .NET classes where they're decorated with the ComVisible(true) attribute.

For example in the documentation sample code here:

http://www.php.net/manual/en/class.dotnet.php

The System.Collections.Stack class is decorated with this attribute:

http://msdn.microsoft.com/en-us/library/system.collections.stack.aspx

As is the System.Windows.Forms.Form class example earlier in this bug report.

However if one tries to instantiate a .NET class without this attribute such as System.Xml.XmlDocument:

http://msdn.microsoft.com/en-us/library/system.xml.xmldocument

Then an exception is thrown:

$xml = new DOTNET('System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089', 'System.Xml.XmlDocument');

Produces:

PHP Fatal error:  Uncaught exception 'com_exception' with message 'Failed to instantiate .Net object [Unwrapped, QI for IDispatch] [0x80004002] No such interface supported

These are my findings from working with .NET 2.0. There seems to be additional problems with instantiating .NET 4 classes because of changes in the way the GAC is used (or not).

Indeed it is like kevin dot kenny said: .NET classes have to be
visible to COM.  Changing to documentation issue.

This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation better.