Skip to content
New issue

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

[Feature Request] Support portable installation #5

Open
tooomm opened this issue May 17, 2020 · 3 comments
Open

[Feature Request] Support portable installation #5

tooomm opened this issue May 17, 2020 · 3 comments

Comments

@tooomm
Copy link

tooomm commented May 17, 2020

I would love to use this portable...

@iklevente-zz
Copy link
Owner

Hello.

ChromiumForWindows works with the Installers, which can be found on https://chromium.woolyss.com/. Because I don't have control over those installers I can not make the actual Chromium browser to install itself into the Portable folder. Although it could be possible by telling the program to create NTFS Symbolic Links, it would mess up the default browser setting in Windows. I would need to do a lot of coding to get it fixed and it might not even work.

You might see that https://chromium.woolyss.com/ has a "Portable" download button at every Chromium branch they have. I could make the Updater to download that instead of the Installer. Well, all of them redirects me to the chrlauncher download site, so that's not an option..

But if you only need the actual ChromiumForWindows Updater to be portable, you can copy everything from C:\Users\YOURUSERNAME\AppData\Local\Chromium\ to your Portable folder. It should run, but it will always create the Schortcuts directed to C:\Users\YOURUSERNAME\AppData\Local\Chromium\ChromiumLauncher.exe not to the actual Portable folder you have created.
To fix this, you will need to build the software without FixShortcuts.cs class and delete the await Task.Run(() => FixShortcut.MakeShortcuts()); Console.WriteLine("Shortcuts are done!"); lines in MainWindow.xaml.cs.

I leave this issue opened, since the NTFS Symbolic Link method might work, but if it won't, I will make sure to at least add an Updater portability option at the Releases page.

@iklevente-zz
Copy link
Owner

Your current best option is to use https://github.com/henrypp/chrlauncher. It is made for portability.
For now, in this project, I will experiment with the portable option, but as I said it will be hard. I will update you if I get some results.

@tooomm
Copy link
Author

tooomm commented May 17, 2020

Your current best option is to use henrypp/chrlauncher.

Will have a look there. Seems like the best option. Thanks for sharing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants