I would like to ask you if you know how to make (at least idea) check on my internal Web (c# .netcore) if I can reach AppInsights.
The purpose is to check if firewall is blocking reachable to AppInsights.
Thank you. Problem is that my web is changing places of hosting - its a reason why I need web (cshtml) visualization if I can reach AppInsights.
Any ideas?
Thank you
There are a few ways you can try:
Method 1:
If the web project has been configured with application insights, just run the web project, and then nav to azure portal -> your application insights, see if the telemetry data are collected; Or you can use tools like Fiddler, when running the web project, check the response of application insights.
Method 2:
Check if these firewall exceptions are set, sample like below:
https://dc.services.visualstudio.com:443
For more details, you can refer to this doc and this doc.
Related
i have a problem i cant host a my web api to public access. For Example, someone from outside to do some requests and get a response. I tried with IIS configuration, all samples try from the GTS, and then there is no movement. Can anyone post me full specs what i need to do to have for example
https://myipaddress:5001/api/ping
visible on public and someone from another machine can execute this request and get a response
IIS is meant for local development. What you want to do is to publish your application. There are many hosting providers, but if we stick to Microsoft, you can use Azure to publish your application:
https://learn.microsoft.com/en-us/azure/app-service/quickstart-dotnetcore?tabs=net60&pivots=development-environment-vs
It is paid, however you can register to get temporary free access to test the solution.
I have recently published my C# .net core Angular 2 web application to an IIS Server. However, the Web Api that I am calling is not working correctly. When I call the Api, a file is supposed to download however, the file does not render correctly.
I am sure that the api is being called as I am not getting a 404 error. When I run the project on my localhost, it works fine, but on the live site it is not working.
One more thing, when I enter information that should normally cause an error in the web api, it is not throwing me an error like it does in the localhost. It is as if the api is failing but when it is published to IIS it doesn't recognize the error in the angular observable. If anyone has any ideas on why this is happening or how I can debug this it would be appreciated. Thanks
Please run the WebApi from IIS individually and check the error.
Please check the file size while downloading because you need to
configure in webconfig file, if exceed default configuration.
Please check in Angular you have subscribe to that observable.
If you can give more details on this. It can help us to provide
more information like specific error and so on.....
I am having this strange problem:
I have just developed a WCF service (on VS2008) and created a website (ASP.net) to use that service. When I launch the website from VS2008, it works fine and I get the "You have created a service method", but if I try to open that service using IIS then it is not able to load the website at all. I get a message that "website found, waiting for reply", but the browser is not able to load the service at all.
Any help will be greatly appreciated!
There was problem with my IIS 7.5, in that ASP.NET was not registered for IIS. The following article was helpful: http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx
I used aspnet_"regiis -i" command and the websites started loading. Thanks for all the help guys!
A few troubleshooting items
Make sure in inetmgr under Web Services Extension that the required frameworks are unblocked.
Enable tracing to watch the messages
Enable exception details in faults
Make sure you are running the website under correct framework (under website properties)
In web.config, clear and add handler svc-Integrated-4.0
I have written some web service, I run it and see it from my firefox and run it from there.
Now I want to call it from some other code/solution i trying to add there a web reference and Web Services on the Local Machine , but i cannot see there my web services.
Any idea what is missing ? Sorry for the newbie question it's my first time with web services.
Thanks.
when you run the web service you will get a url in browser.Copy that, in reference of your project Add Webreference , it will ask for the url paste it and click go.Add that to your project.
If you are not added in IIS. please add it to IIS and do the rest of operation.other wise when you try for that you wont get the web service.
Or run web service in visual studio debugger and dont close and to the operations.
please also ref: http://msdn.microsoft.com/en-us/library/d9w023sx(VS.80).aspx
If you created the Web service project in a file system, then it ll automatically assign the temporary port number to run the service. In this case you cannot see the service in other projects.
Try creating the IIS virtual directory for the web service and see.
I have read a lot about impersonation, and I have tried a ton of tags in my config file. I have tried [OperationBehavior(Impersonation = ImpersonationOption.Required)] on my method that hits the database.
None of it works. I get a wide variety of error messages depending on how my config is setup.
Can anyone lay out for me what C# and configuration (ie bindings, behaviors, endpoints settings) is needed to get the following scenario to work:
I call a WCF method via WCFTestClient.
The WCF Method is hosted in IIS (running under an IIS user that is not a valid user in the DB).
That method sees who the caller is and passes those credentials on to the call to the database
The Call to the database is in a different project (a class library) and uses Linq-to-sql
The database performs the action as if the caller of the WCF service had done it.
If anyone has clarified this mystery please share the details with me.
Thanks!
(NOTE: I am developing in Visual Studio 2010 Ultimate and hosting in IIS 7)
There is a nice walkthrough of how to set up impersonation in WCF here. You may be missing the servicebehavior setting?