-
Notifications
You must be signed in to change notification settings - Fork 15
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
Binding redirects lost because of manual relaunching of tool #49
Comments
Not sure if this will work, maybe there's an alternative to dispatching, but I explained why this is necessary at https://github.com/dotnet/cli/issues/6028#issuecomment-346250164. |
Relating #51 because it might be important to the goal of this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
DotnetToolDispatcher
is used to re-launch the tool at runtime. Because of this manual relaunching all the magic that dotnet cli does (like taking care of the binding redirects) is lost.I'll try to strip out this part in the coming days and simply try calling
Worker.Execute()
at that point.See: https://github.com/dotnet/cli/issues/6028#issuecomment-346174568
The text was updated successfully, but these errors were encountered: