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

Add instructions for Windows Store Electron apps #53

Merged
merged 2 commits into from
Nov 11, 2017

Conversation

miloszfalinski
Copy link
Contributor

Based on my research with adding AutoLaunch into the Paws for Trello Windows Store release.

Based on my research with adding AutoLaunch into the Paws for Trello Windows Store release.
README.md Outdated

If you have your Electron-based app in the Windows Store and would like to include auto launch functionality, simply linking to the executable path will not work. The Appx packages required for Electron are sandboxed and the install location can only be accessed by the system itself.

There is a way to bypass that - it will require you to know the developer ID, app ID and package name of your app. Then, instead of using the exec path, you will need to set the path in `AutoLaunch()` config to: `explorer.exe shell:AppsFolder\DEV_ID.APP_ID!PACKAGE_NAME`. You can find your apps details following [this article](http://winaero.com/blog/exclusive-how-to-start-a-modern-app-from-desktop-without-going-to-the-metro-start-screen/). Note that you might need to compile and submit your app to the store first to obtain these details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this. There's just one tiny mistake here. I think it should say "You can find your apps details by following"

@miloszfalinski
Copy link
Contributor Author

@adam-lynch You're right - fixed now!

@adam-lynch adam-lynch merged commit a6cf594 into Teamwork:master Nov 11, 2017
@adam-lynch
Copy link
Contributor

Thanks for this! You probably didn't see #64 but we're looking to bring add some contributors/maintainers to help with:

  • Improving documentation.
  • Troubleshoot, triage, and reproduce issues on your machine.
  • Fix bugs.
  • General maintenance (dependencies, etc).
  • Suggest & add features.
  • Review, test, and merge pull-requests from other contributors.
  • Anything else you can think of which would help.

Would you be open to that? I can give you access.

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

Successfully merging this pull request may close these issues.

2 participants