Hi,
normally, mfcEmbed's own file location provider should make the program store its profile stuff under
<Application Data folder on user's machine>\MfcEmbed.
Nevertheless, mfcEmbed also creates a directory
<Application Data folder on user's machine>\Mozilla
during start (but doesn't fill it), if this doesn't exist before. My debugger told me, that was because nsAppFileLocationProvider::GetProductDirectory() was called. But this file location provider shouldn't be active any more due to the NS_InitEmbedding() call with mfcEmbed's own provider, should it???
That's right. The default provider (nsAppFileLocationProvider) should not be used, since MfcEmbed supplied its own. Sounds like there's a bug. I'll take a look.
-Conrad
Is this a known bug? Or even a feature? I absolutely want to avoid that the profiles of my embedding app and Mozilla (if installed) get mixed. Is there any danger due to this effect?
Thanks for any answers, Florian
