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

Shortcut Support #135

Open
kimmknight opened this issue Sep 20, 2024 · 1 comment
Open

Shortcut Support #135

kimmknight opened this issue Sep 20, 2024 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@kimmknight
Copy link
Owner

  • Allow creating, editing, and exporting of RDP files for applications that refer to .lnk files (without crashing).
  • When adding a RemoteApp and a shortcut is selected (instead of an exe), allow the option to preserve the shortcut path instead of resolving it to the exe.
@kimmknight kimmknight added bug Something isn't working enhancement New feature or request labels Sep 20, 2024
@kimmknight
Copy link
Owner Author

Currently, when adding a remoteapp and selecting a .lnk file, the resolved exe path is returned by the OpenFileDialog. It's not RemoteApp Tool resolving it.

According to this post, you can allow selecting lnk files by using OpenFileDialog.DereferenceLinks.

But my guess is that most users want lnk files resolved to exe files. So how might RemoteApp Tool provide the option to select .lnk files, without adding any complication to the process of adding an app (for normal users), and without cluttering the UI?

I have not investigated, but I believe there is a way to customize the OpenFileDialog. If so, perhaps a checkbox could be added "Don't resolve shortcuts" (unticked by default).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant