In the end, deploying a web application generally involves copying the files to a location on the server that the site is to be served from, so its really a rather simple process.
Don't try to tie your source control instance to your deployment directly. instead use your development environment to provide any additional assistance you need during deployment. Continuous integration is great for testing and development, but don't turn it into continuous deployment. GIT is a great tool, but its not specific to any particular executing environment, and it would be unreasonable to expect it to be able to perform deployment ops to all the different kinds of httpds and database platforms.
so, initially, build your IIS site, and configure it as needed. I'd recommend using virtual directories, instead of serving the site directly from inetpub\www\. that allows you to preserve older versions, and to quickly change between them as needed.
then when you deploy, copy your code up to the server (I usually put mine in a folder with the TFS changset number, so you'd use some GIT generation number instead) and once copy is complete, just point the virtual directory to the new version of the app.
https://github.com/projectkudu/kudu - posted it here to as it does exactly what you want – bbqchickenrobot – 2016-05-04T20:09:18.413