He (being a 64-bit user) already knew what it was likely to be but it opened up an interesting “angle” for me.
Now…my application uses the WebBrowser control from .NET 3.5 Sp1 so this means that on a 64-bit platform we’ll have;
64-bit executable –> 64-bit web browser –> Silverlight plug in
and because there’s no 64-bit version of Silverlight, that’s going to cause a problem.
I’ve tried to re-work the application as 32-bit only which should solve the problem for now but it was interesting to me that I managed to bring in a 32-bit-only component without even noticing!