Can't debug my asp.net web app developped on visual studio 2015 and hosted on IIS

Question

I am a telecom engineer, I have studied a little bit of coding but I am not a professional, I have to develop ac# asp.net app for my company and I have some issues with debugging my app with Visual Studio 2015. I hosted my app on IIS (not IIS Express, even if I don't understand the difference), when I hit debug (with Firefox, Google Chrome...) a message of error displays where it is written:

unable to start debugging on the web server the remote server returned an error 400

I have litterally tried everything, can you please help me and give me solutions that I will understand (I am no professional), if you need a screen shot or something please let me know.

Answer 1

Clarifications/details (based on comments, etc.), and since "just use localhost/foo" sounds too magical:

• if you're debugging on a remote web server (not your own PC), you'll have to setup the remote machine to allow such . This may or may not be feasible (not your server, etc. etc.).

• Hence Visual Studio provides local debugging ( Express or local IIS )

• What is IIS Express ?

---

When I want to start a project I can eather store it on IIS or IIS Express

Sure, but you'll have to know how to set things up (see links)

When I use IIS, and click on debug, I have error 400 and the browser doesnt open But When I use IIS Express and click on debug, it debugs, the browser opens and I have a 500.52 error

Set debug=true . It should give you error/exception detail(s) (also in link above)

So I am storing my project on IIS (inetpub\\wwwroot...) and when I design and write my code I just press start without debug and the browser opens with my app appearing

Same as above, that just means IIS is running your app just like any other ASP.Net app. It does not automatically mean you can attach to it and debug .

While you can certainly develop that way (using /wwwroot), you'll be better off deving in your own directory, using VS/IIS Express, and publish to IIS (as simple as file system copy). You'll also learn what publish means (compiling), what in all your code is "published"/needed in live/production. If you kept deving in IIS the way you are, you'll likely not know the difference.

IIS admin is a bigger topic (multiple apps, multiple sites, and associated configuration).