Closed Bug 322053 Opened 20 years ago Closed 18 years ago

DllRegisterServer and plugin NPAPI

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: charon, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8) Gecko/20051111 Firefox/1.5 With the old method install.js I can (un)register the dll plugin after (un)install. With install.rdf it's not possible. Can you after install of plugin call the method plugin export DLL DllRegisterServer et after uninstall the method DllUnregisterServer Reproducible: Always
The recommended technique, as I understand it, was to do the required setup steps at the first run. I don't understand this particular bug though. CC bsmedberg, who wontfixed a similar (in that it related to install.rdf and DLLs :P) bug.
(In reply to comment #1) > The recommended technique, as I understand it, was to do the required setup > steps at the first run. I don't understand this particular bug though. > > CC bsmedberg, who wontfixed a similar (in that it related to install.rdf and > DLLs :P) bug. > I try me explain. English is not my native language. I'm the developer/webmaster of ma-config.com website. It's an original project who detects the hardware from website(an everest/ sisoft but on a web page). This project is very known in france. The plugin is too used by other websites as touslesdrivers.com(60000 visitors by day). My plugin works on IE/firefox/netscape under Windows. I want to work the plugin with the new system of installation. But if you delete the plugin(with the driver) without unregister. The driver is unregistered and deleted. It's not clean.
Also, bug 322050 is along similar lines as this one
(In reply to comment #3) > Also, bug 322050 is along similar lines as this one > Yes but it's not the same. For the bug 322050 the reboot of firefox after install of plugin (with install.rdf) breaks user experience. The install method with install.js permit to refresh plugins without reboot of firefox
Perhaps the operative question here is why you're dllregistering DLLs from an extension... since extensions typically live in the user's profile, it would at best be user-specific registration. Typical NPAPI plugins don't need to be dllregistered. Perhaps this bug is about the fact that we have to restart firefox to install the extension and find the plugin?
(In reply to comment #5) > Perhaps the operative question here is why you're dllregistering DLLs from an > extension... since extensions typically live in the user's profile, it would at > best be user-specific registration. Typical NPAPI plugins don't need to be > dllregistered. > > Perhaps this bug is about the fact that we have to restart firefox to install > the extension and find the plugin? > For the bug 322053 Yes my registration is admin specific. I use not DllRegisterServer for COM registration but for install a driver in manual mode. With install.js I use File.windowsRegisterServer.But the plugin and driver is not uninstall. With install.rdf(em:type to value 16) the file driver is deleted but not unregistered.If the driver is loaded at uninstall it's not clean. I know that NPAPI standard not permit install/desinstall. But Is a future install.rdf will can permit a call similar to File.windows(Un)RegisterServer in install.js? The new method with install.rdf must permit an install/desintall clean contrary to install.js. For the bug 322050 I don't understand why I must restart firefox after install for loading NPAPI plugin. With the old method it was possible(refreshplugins). It' not specific to my plugin. See the example to midi plugin. It must not difficult to correct. Thank you for your answers :)
Looks like there was no progress here and we no longer support plugin type add-ons so I think what you are asking for is a WONTFIX.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.