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.

Sign up for GitHub

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

Jump to bottom

When starting the generator via Rider, plugins are searched in C:/Program Files/dotnet/plugins #35

Closed
janhohenheim opened this issue Apr 9, 2020 · 2 comments
Closed

When starting the generator via Rider, plugins are searched in C:/Program Files/dotnet/plugins #35

janhohenheim opened this issue Apr 9, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@janhohenheim
Copy link
Contributor

No description provided.

@janhohenheim janhohenheim added the bug Something isn't working label Apr 9, 2020
@janhohenheim janhohenheim changed the title When starting the generator via Rider, plugins are expected to be in C:/Program Files/dotnet/plugins When starting the generator via Rider, plugins are searched in C:/Program Files/dotnet/plugins Apr 9, 2020
@FreeApophis
Copy link
Member

So, what is the current way to find the executables path working EVERYWHERE!?

@bash
Copy link
Contributor

bash commented Apr 15, 2020 •
edited
Loading

There's System.AppContext.BaseDirectory. Keep in mind that that points to a temporary directory when doing a single file publish. See: dotnet/runtime#3704

FreeApophis added a commit that referenced this issue Apr 16, 2020
@FreeApophis
Merge pull request #44 from messerli-informatik-ag/fix-rider-plugin-s…
d434dbe 
…earch

Fixes #35 - Use AppContext.BaseDirectory to detect the plugins path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@FreeApophis @bash @janhohenheim