Recently I came across an issue in TechNet which was quite interesting.
Issue:
I was able to publish two Mozilla Firefox (41.0, 49.0) to a client machine. I've added Desktop Icons with the respective version on it to differentiate one from the other.
If I open them individually, not keeping both opened, I can confirm the version of the browser checking the Help otpion, however if I open one browser say 41.0, keep it opened, then open the second browser version 49.0 , the first browser version 41.0 will take precedensce on the second instance too.This can be checked by opening up help and checking the version. The second window showed 41.0 version even though it was 49.0 version firefox shortcut.
https://social.technet.microsoft.com/Forums/en-US/c364b975-a2e4-425f-8d4c-88fdc7550599/having-two-mozilla-firefox-versions-from-appv-published-to-a-computer-if-i-open-both-versions-one?forum=mdopappv&prof=required
Solution:
Edit the dynamic config file and add the below -no-remote in the <Arguments> tag. -no-remote will tell the FireFox to use a new instance of it while opening, if we don't pass the argument then it will open a new window but it will be the same instance of previously opened FireFox.
<Shortcuts Enabled="true">
<Extensions>
<Extension Category="AppV.Shortcut">
<Shortcut>
<File>[{Programs}]\Mozilla Firefox.lnk</File>
<Target>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</Target>
<Icon>[{Windows}]\Installer\{xxxxxxxxx-0B398xxxxxxF}\Icon_firefox1.exe.0.ico</Icon>
<Arguments> -no-remote </Arguments>
<WorkingDirectory>[{ProgramFilesX86}]\Mozilla Firefox\</WorkingDirectory>
<ShowCommand>1</ShowCommand>
<ApplicationId>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</ApplicationId>
</Shortcut>
</Extension>
</Extensions>
</Shortcuts>
Save the deploymentconfig/user config file and add it while publishing.
Reference - http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile
Issue:
I was able to publish two Mozilla Firefox (41.0, 49.0) to a client machine. I've added Desktop Icons with the respective version on it to differentiate one from the other.
If I open them individually, not keeping both opened, I can confirm the version of the browser checking the Help otpion, however if I open one browser say 41.0, keep it opened, then open the second browser version 49.0 , the first browser version 41.0 will take precedensce on the second instance too.This can be checked by opening up help and checking the version. The second window showed 41.0 version even though it was 49.0 version firefox shortcut.
https://social.technet.microsoft.com/Forums/en-US/c364b975-a2e4-425f-8d4c-88fdc7550599/having-two-mozilla-firefox-versions-from-appv-published-to-a-computer-if-i-open-both-versions-one?forum=mdopappv&prof=required
Solution:
Edit the dynamic config file and add the below -no-remote in the <Arguments> tag. -no-remote will tell the FireFox to use a new instance of it while opening, if we don't pass the argument then it will open a new window but it will be the same instance of previously opened FireFox.
<Shortcuts Enabled="true">
<Extensions>
<Extension Category="AppV.Shortcut">
<Shortcut>
<File>[{Programs}]\Mozilla Firefox.lnk</File>
<Target>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</Target>
<Icon>[{Windows}]\Installer\{xxxxxxxxx-0B398xxxxxxF}\Icon_firefox1.exe.0.ico</Icon>
<Arguments> -no-remote </Arguments>
<WorkingDirectory>[{ProgramFilesX86}]\Mozilla Firefox\</WorkingDirectory>
<ShowCommand>1</ShowCommand>
<ApplicationId>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</ApplicationId>
</Shortcut>
</Extension>
</Extensions>
</Shortcuts>
Save the deploymentconfig/user config file and add it while publishing.
Reference - http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile
No comments:
Post a Comment