TO DO for Performance Improvement: We are loading every dll in the components directory and instructing it to auto-register. Could we have a utility that does this similar to regsvr32. This also takes a lot of time when first initializing AppRunner. For some reason the initialization code seems to load the components even after they are auto-registered.
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M7 → M8
We need this and have to turn off autoregister. But before that we need to work out the registry problems and decide where it is going to be. The registry stuff will work out in M7. Moving this to M8.
Assignee: dp → chofmann
Status: ASSIGNED → NEW
Target Milestone: M8 → M9
We have this utility. xpcom/test/regFactory Once the installer is ready, we will need to use this in the installer. M9 and moving it to installer group.
Assignee: chofmann → cathleen
Summary: Need a utility similar to regsvr32 → [feature] performance on first launchy reqs. xpcom/test/regFactory hook up in installer
changing the summary and moving over the cathleen to set target milestone and get this baby hooked up.
Summary: [feature] performance on first launchy reqs. xpcom/test/regFactory hook up in installer → [feature] performance on first launch reqs. xpcom/test/regFactory hook up in installer
Assignee: cathleen → ssu
Component: Build Config → Install Wizard
OS: Windows 95 → All
Hardware: PC → All
Target Milestone: M9 → M10
change component to Install Wizard. setting target milestone to M10. reassign to Sean (for win), ccing Samir (for mac), Dan, Cathleen & DP. DP, I assume this utility exists on Mac too, correct?
Setting QA Contact to gbush to keep her in the loop.
The wizard now launches apprunner with a -installer parameter at the end of the install. If autoregistering is suppose to be happening only with the -installer flag now, then this bug is fixed for Windows. If the -installer is not the fix for this bug, someone please provide more information. I'm leaving this bug open because the Mac is probably not done yet.
I will take this bug. I need to make: - -installer do autoreg instead of always - use buildID and run autoreg only if the buildID changed for release builds only - Land relative pathnames in registry - Ship component registry along with the release
Dp, do you think using a different flag (other than -installer) to run the autoreg might be useful? I'm thinking of the situation when the user simply wants to autoreg, not also go through the entire profile migration. This way the profile migration and the autoreg can be run either independent of each other or together at the same time (like apprunner.exe -installer -autoreg) Just a thought.
xpinstall will be able to run autoreg apart from the -installer flag, and power users will be able to manually call RegFactory.exe (which I'd rename to regcomp or compreg). Would blowing away the component registry trigger an AutoReg?
Yeah there are ton of ways to get to autoreg. So I dont think another flag would be more useful.
We are in home stretch. component.reg can be shipped. regfactory has been updated to do autoreg if run with no arguments. But release cant run it because it is a test/ and they dont compile tests. Need to move regFactory to something like xpcom/registry
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
Is there any more clean up work to do here? OR is this totally Resolved/Fixed now? Wanted to check before marking Verified. Thanks!
Checked with dp..cool to mark Verified.
Updating component from Install Wizard to Installer.
You need to log in before you can comment on or make changes to this bug.