We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are 2 strange things going on with the registry key path.
To address both problems, we should force the registration of the coapp path in both Wow6432Node and not-Wow6432Node.
I'm not sure yet how to do that, but that seems the right approach.
This would also solve the problem of mixing up different bits-version of Firefox/CoApp/Firefox.
See #195 and #201.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There are 2 strange things going on with the registry key path.
To address both problems, we should force the registration of the coapp path in both Wow6432Node and not-Wow6432Node.
I'm not sure yet how to do that, but that seems the right approach.
This would also solve the problem of mixing up different bits-version of Firefox/CoApp/Firefox.
See #195 and #201.
The text was updated successfully, but these errors were encountered: