Hi, I've completed development of an XPCOM component and tested it on Firefox v1.0.2, Netscape v7.2 and Mozilla v1.7.6 - it works just fine on all of these. The problem I'm having is on the deployment side. I need to deal with the situation where my dll will be installed on a machine before the browser. I've been reading an article on mozilla.org called "The First Install Problem -- Plugin IDs and the Win32 Registry" (http://www.mozilla.org/projects/plugins/first-install-problem.html) - this looked like just the ticket - however after trying it out and digging around for other help I still haven't been able to solve this first install problem. I'm not 100% sure if this article is just a proposal on how to deal with this problem or if it's actually describing a solution that has been implemented on Gecko based browsers? If it is describing a solution that should work then has anyone any ideas why it might not be working for me (I'm trying it with Mozilla 1.7.6 on WinXP Pro) - I've followed the instructions as given but without any success. Note: my XPCOM component is very simple, there's no .xpt file (just a dll), I don't rely on MIME types or suffixes - it simply plugs into the browser and uses a progress listener to listen for page downloads. So to summarize, I need a solution where I can install my XPCOM component dll on a machine with no Gecko browser - then when a browser is eventually installed on the machine it will automatically pick up details of the already installed XPCOM component and use it. Does anyone know any other way that I can solve this problem or has anyone any suggestions on where best to look for an answer? Obviously the ideal for me would be a single solution that worked for all the Gecko based browsers I need to support, but if I could even get a solution for one of them it would be a start and I could take it from there.
Thanks, Damien
<<attachment: winmail.dat>>
