[webkit-dev] Removing of COM registration in Windows builds means C# .Net clients can no longer be built?

[Julian Jacques Maurer]

Maybe you can register the DLL using dumprendertree - I want to try this but
I'm still building WebKit.

 

 

Does anyone know how to generate C# clients for WebKit since COM
registration has been removed from trunk?

 

As per 

 

Changeset 36245 <http://trac.webkit.org/changeset/36245>  for
trunk/WebKit/win/ForEachCoClass.cpp
<http://trac.webkit.org/browser/trunk/WebKit/win/ForEachCoClass.cpp?rev=3624
5> 

Changeset 34346 <http://trac.webkit.org/changeset/34346>  for
trunk/WebKit/win/ForEachCoClass.cpp
<http://trac.webkit.org/browser/trunk/WebKit/win/ForEachCoClass.cpp?rev=3434
6> 

 

COM registration is no longer performed and reg-free COM used instead.

 

This is fine for C++ native clients (example being WinLauncher app), as
Manifest tool supports creating the appropriate assembly manifest for
reg-free COM without referenced 

 

But as far as I know (and as per
http://msdn.microsoft.com/en-gb/magazine/cc188708.aspx) attempting to write
a C# client is now problematic. In Msdev2005 C# supports isolated COM dlls
for deployed build, but the COM component needs to be registered on the
development machine. 

 

So now would get following building a C# client using WebKit "Error
71           Problem isolating COM reference 'WebKit': No registered classes
were detected for this component"

 

So - anyone ideas for building C# clients for WebKit since COM registration
has been removed from trunk?

 

Many thanks.

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.webkit.org/pipermail/webkit-dev/attachments/20080927/b94a34a1/attachment.html