6 hours ago, RealBboy360 wrote
I'm talking about a Azure website running asp.net web api with it's own web.config and iis. VS the Azure web services api
Huh ? an "Azure Website" is running IIS with a web.config *if* the platform you pick is .net.
"Azure web services api" that is not a thing.
do you mean the API service ?
if we go to the video (as I have not had time yet to do it myself)
one of the demos was to create a web api.... they had a controller and hooked up some code so that the controller retuned data... nothing crazy,
they did say that the api app service has an open source tool that provides json meta-data to help with describing and consuming the api you create.
no dark secret there it's still just iis running asp.net and a nuget package.
get this: azure anything is a vm running windows server or Linux
if you want uber control you can have it by paying for a higher level option and you can rdp into the server and do what you want.
but like any hosting system the lower cost levels give you less admin access so they can make a shared server.
the add on to that is that they have worked out how to swap out vm's manage a lot of servers and make it all as simple as they could for us to setup and manage.
the only part that is different is the thing where they allow you to take a bunch of service calls and hook them together , ok that they did not show a coding session for, possibly that is what you are actually worried about ??
I bet that also can be coded and if you do not like it then do not use it but that is a small part of th whole deal.