You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Brief research shows that it's impossible to use Process.Start(url) in .net core to open default browser.
Trivial possible fix:
Replace line 44: Process.Start(authorizationUrl);
with
Console.WriteLine("Visit the following url: ");
Console.WriteLine(authorizationUrl);
We interact with user via console anyway, so instead of assuming there's a possibility of opening url on any given platform it might be better to ask the user to interact with server.
The text was updated successfully, but these errors were encountered:
Phoenix-
changed the title
PromptCodeReceiver causes FileNotFoundException on .Net Core
PromptCodeReceiver causes FileNotFoundException on .Net Core, Windows
Aug 14, 2016
Thanks for filing this issue. Yes, we're aware of the problem (but had failed to create an issue for it - oops) and expect to fix it before the next release. Probably using the fix you suggest.
chrisdunelm
added a commit
to chrisdunelm/google-api-dotnet-client
that referenced
this issue
Aug 15, 2016
In .NET Core prompt the user to browse to the authentication URL, rather than launch a browser. Opening a URL as a process is not supported on Core. Fixesgoogleapis#813
In .NET Core prompt the user to browse to the authentication URL, rather than launch a browser. Opening a URL as a process is not supported on Core. Fixesgoogleapis#813
In .NET Core prompt the user to browse to the authentication URL, rather than launch a browser. Opening a URL as a process is not supported on Core. Fixes#813
Brief research shows that it's impossible to use Process.Start(url) in .net core to open default browser.
Trivial possible fix:
Replace line 44:
Process.Start(authorizationUrl);
with
We interact with user via console anyway, so instead of assuming there's a possibility of opening url on any given platform it might be better to ask the user to interact with server.
The text was updated successfully, but these errors were encountered: