Azure-docs: Unable to successfully call API from ASP.NET web app

[mattfortech]

Hello,
I have successfully tested the console application, but I am unable to get a near identical implementation using an ASP.NET web application. I keep getting the following exception: "{"Operation returned an invalid status code 'NotFound'"}"
I thought at first that it was a result of not being able to elect the iteration I am using as "Default", but that didn't seem to pose an issue in the case of the console application.
Can I humbly request that someone show an example of calling the API using C# ASP.NET page?
Thank you!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 30bf4241-72f9-3227-d8f8-855da83e4da1
• Version Independent ID: c8787c68-f4c9-6689-5c7f-0c6bfc3d1797
• Content: Quickstart: Create an image classification project with the Custom Vision SDK for C#
• Content Source: articles/cognitive-services/Custom-Vision-Service/csharp-tutorial.md
• Service: cognitive-services
• Sub-service: custom-vision
• GitHub Login: @anrothMSFT
• Microsoft Alias: anroth

[RohitMungi-MSFT]

@mattfortech Thanks for the feedback. We are investigating into the issue and will update you shortly.

[RohitMungi-MSFT]

@mattfortech Here is a sample project from AndyButland that does exactly the same thing and more as this quickstart but it is implemented by three projects, an ASP. NET Core MVC web application, an Azure Functions application, and a class library project that contains common services and settings used by the other two.

You will need Visual Studio. NET 2017, Azure storage emulator to interact with azure storage in a local dev environment and Azure storage. Azure Storage Explorer is also useful in order to view the contents of Azure storage components such as blob containers.

This project is also explained by this course at plural-sight.

@anrothMSFT Do we have any plans to add a ASP .NET web application quickstart in the future?

[mattfortech]

@RohitMungi-MSFT Thank you so much for your help. I am using the .NET SDK quickstart guide as a hybrid approach (console instructions to web app implementation) in the meantime. As I mentioned, I keep getting the 'Not Found' output. I am just not sure if this is a result of the missing "Default" option or if I am doing something wrong?
It's not much more than 20 lines of code, I am wondering if I can maybe post it somewhere to show you or @anrothMSFT my approach, someone might be able to shed some light. Then you can use what I have for a web app quickstart? Thanks again!

[RohitMungi-MSFT]

@mattfortech You can post the same in MSDN Cognitive Services forum for anything specific to code and share that link here. The GIT issues here are used for any bugs in documentation.

Could you also confirm if which version of custom vision client was used for your console application test? I used the latest version 1.0.0 and the steps in this quickstart do not work as expected.

@areddish The sample code at github repo is not updated and the steps in this documentation also need to be updated.

1. For CreateImagesFromData() we need to now pass a list of Guid's of the tags that are created instead of a string.
2. How can we retrieve the predictionid that needs to be passed to PublishIteration()? I could not find a way to get the id even from the custom vision page while publishing from the portal.

Due to these errors this quickstart does not run successfully for the newer version the packages.

[areddish]

@RohitMungi-MSFT - Repo is now updated.

The prediction id is available in the settings page of the custom vision portal. For each Azure resource it shows the training key, endpoint, and resource id. You can also use the azure portal to find the custom vision prediction resource. Here's where to find it in the custom vision portal:

[RohitMungi-MSFT]

@areddish Thanks for the update. @mattfortech with the updated quickstart the application runs successfully for the console application. You can check the same for your web application too.

We also have a thread in the MSDN forum for the same request. So, we can track the same for .NET webapp there. We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply. We will gladly continue the discussion and we will reopen the issue.