16,008,175 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Tony Girgenti (Top 5 by date)
Tony Girgenti
13-Jul-18 13:45pm
View
Deleted
I can't say that I figured this out, but I did manage to get it to work by testing different coding strategies especially inspired from this article: https://msdn.microsoft.com/en-us/magazine/mt846469.aspx by Dino Esposito.
I created a button to "GetProducts" and modified the bottom in the AccessToken.cshtml file like this:
"
function startTask() {
$.get("/products/getproducts/");
}
document.getElementById("get-products-button").addEventListener("click", event => {
event.preventDefault();
});
"
I added the bottom script just as a debugging aid to see if the button was being activated.
Without any part of the above code, the messages to the client do not work. I can't explain that, I just know that if I remove any part of it, it does not display the messages to the client.
The messages to the client do display, but this success comes at a price. When the GetProducts method gets to this line:
return View("~/Views/API/Products.cshtml", multipleProductModel);
It does not display the Products.cshtml view screen. It does not give an error, it just does not display.
The GetProducts method processes the way it should, but it won't display that view.
I would appreciate it if anyone can tell me why that view will not display.
Thanks,
Tony
Tony Girgenti
13-Jul-18 8:03am
View
Thank you Nelek. It's nice to know that I did something right.
Tony
Tony Girgenti
17-Jun-18 9:03am
View
Hello,
Yes, I did read that several times. Although it contains a good explanation of the OAuth flow, I don't see anything in there related to my problem of not executing the method in the redirect Url.
Thanks,
Tony
Tony Girgenti
16-Jun-18 14:13pm
View
The problem is when it returns from an authorization call to the server, it does not execute the return method specified in the redirect url.
When I take it through the Visual Studio 2017 debugger, the authorization string sent to the server is the same as when I run it in the .Net 4.5.2 version of the client.
When it returns from the server in the .Net 4.5.2 client, it executes a method.
When it returns from the server in the .Net Core 2.0 client, it does not executes that method. It just hangs up with no error message.
Tony Girgenti
16-Jun-18 13:56pm
View
The problem is when it returns from an authorization call to the server, it does not execute the return method specified in the redirect url.
When I take it through the Visual Studio 2017 debugger, the authorization string sent to the server is the same as when I run it in the .Net 4.5.2 version of the client.
When it returns from the server in the .Net 4.5.2 client, it executes a method.
When it returns from the server in the .Net Core 2.0 client, it does not executes that method. It just hangs up with no error message.
Thanks,
Tony