Click here to Skip to main content
16,020,080 members
Home / Discussions / C#
   

C#

 
AnswerRe: Unable to Receive data from Cobas e411 Serial Port Pin
Gerry Schmitz28-Jun-23 6:51
mveGerry Schmitz28-Jun-23 6:51 
QuestionGoogle PeopleAPI & HttpListener Redirect URI Pin
Kevin Marois22-Jun-23 10:03
professionalKevin Marois22-Jun-23 10:03 
AnswerRe: Google PeopleAPI & HttpListener Redirect URI Pin
jschell23-Jun-23 10:45
jschell23-Jun-23 10:45 
GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
Kevin Marois23-Jun-23 12:18
professionalKevin Marois23-Jun-23 12:18 
GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
Richard Andrew x6425-Jun-23 11:44
professionalRichard Andrew x6425-Jun-23 11:44 
GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
Kevin Marois25-Jun-23 17:41
professionalKevin Marois25-Jun-23 17:41 
GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
jschell26-Jun-23 5:31
jschell26-Jun-23 5:31 
GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
Kevin Marois26-Jun-23 8:20
professionalKevin Marois26-Jun-23 8:20 
I agree, and I'm not sure how else I would do this.

What it comes down to is waiting for the OAuth to complete and getting the reponse url. Do you know of any other way of doing this other than using an HTTPListener?
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.

GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
Kevin Marois26-Jun-23 16:19
professionalKevin Marois26-Jun-23 16:19 
GeneralRe: Google PeopleAPI & HttpListener Redirect URI Pin
jschell27-Jun-23 4:48
jschell27-Jun-23 4:48 
General[UPDATE] - Google PeopleAPI & HttpListener Redirect URI Pin
Kevin Marois27-Jun-23 6:01
professionalKevin Marois27-Jun-23 6:01 
GeneralRe: [UPDATE] - Google PeopleAPI & HttpListener Redirect URI Pin
jschell28-Jun-23 5:54
jschell28-Jun-23 5:54 
QuestionThreading related naming and usage of const Pin
HobbyProggy20-Jun-23 5:04
professionalHobbyProggy20-Jun-23 5:04 
AnswerRe: Threading related naming and usage of const Pin
Richard Deeming20-Jun-23 6:05
mveRichard Deeming20-Jun-23 6:05 
GeneralRe: Threading related naming and usage of const Pin
HobbyProggy20-Jun-23 23:02
professionalHobbyProggy20-Jun-23 23:02 
GeneralRe: Threading related naming and usage of const Pin
Richard Deeming20-Jun-23 23:26
mveRichard Deeming20-Jun-23 23:26 
GeneralRe: Threading related naming and usage of const Pin
HobbyProggy21-Jun-23 2:02
professionalHobbyProggy21-Jun-23 2:02 
GeneralRe: Threading related naming and usage of const Pin
Richard Deeming21-Jun-23 2:22
mveRichard Deeming21-Jun-23 2:22 
GeneralRe: Threading related naming and usage of const Pin
HobbyProggy21-Jun-23 3:16
professionalHobbyProggy21-Jun-23 3:16 
GeneralRe: Threading related naming and usage of const Pin
harold aptroot20-Jun-23 15:07
harold aptroot20-Jun-23 15:07 
GeneralRe: Threading related naming and usage of const Pin
HobbyProggy20-Jun-23 23:04
professionalHobbyProggy20-Jun-23 23:04 
AnswerRe: Threading related naming and usage of const Pin
Gerry Schmitz21-Jun-23 4:42
mveGerry Schmitz21-Jun-23 4:42 
AnswerRe: Threading related naming and usage of const Pin
jschell23-Jun-23 10:53
jschell23-Jun-23 10:53 
GeneralRe: Threading related naming and usage of const Pin
HobbyProggy6-Jul-23 3:55
professionalHobbyProggy6-Jul-23 3:55 
QuestionMonospaced font (i.e. "Terminal" font in FontDialog Pin
Ronald Boucher14-Jun-23 12:53
Ronald Boucher14-Jun-23 12:53 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.