Last post Nov 30, 2017 11:29 PM by PatriceSc
Nov 30, 2017 07:20 PM|tbowen01|LINK
I have an ASP.Net Core site with a page that has a button on it to upload documents to a database. The upload button, when clicked, calls an API on a different server, and that API processes the document. I built it with .Net Core 1.1. I have recently installed
.Net Core 2.0. The original solution will not build now. I created a new 2.0 solution and recreated all of the code, pages, etc. It runs, but when I click the button to run the upload, all I get is a refreshed page. No error. Once the file is inserted, it
is supposed to redirect to another page. The insert is not working, as there is no data being put in the database. But with no error being returned, I not sure what is happening. Is there a way to ensure that the API is being called? Also, the original solution
does not compile or run, as I mentioned. It's unable to find nuget packages. Is there a way to address that?
Nov 30, 2017 07:45 PM|Dmitry Sikorsky|LINK
Hi! Could you share some code? Is uploading done on the client side or server side?
Nov 30, 2017 07:49 PM|PatriceSc|LINK
This is a server application that calls another server using HttpClient? Don't you have still a EnsureSuccessCode to throw if the call fails ? Make sure you are not hiding exceptions.
Nov 30, 2017 09:02 PM|tbowen01|LINK
The code resides on a different network. There is no way for me to move it. I'd have to re-type it. I use the file upload control on the client to upload the file to the server,
Nov 30, 2017 11:29 PM|PatriceSc|LINK
And you don't even have access to this server to check an exception log or something like that?
Unless the application is written to pretend that all goes well when it's not the case I never have seen an application to malfunction without any sign somewhere even if it sometimes a bit hidden (for example having to use F12 in a browser to see a message
on the console or an http request to a 3rd party that returns some error http status code).
You need first to find an error message or to understand what happens and how it differs from what you expect to be then able to fix the issue you found.