Typically, the person who clicked on a release should visit after he uploaded the site only for sake verification (make sure that nothing was bombed). But if you are looking for a programmatic approach, WebClient might be useful ...
using (WebClient client = new WebClient()) { client.DownloadString("http://wwww.sitename.com/"); }
Then make it exe and use the window scheduler to start it. You could even put this in WinService and report the status of the log file.
Update:
It seems that VS2012 now opens the page after publication, as a result of which clicking on the site is the first request.
In addition, if you find that you have to visit it often (every 15 minutes, as mentioned in the question), you may want to reconsider the IIS / AppPool configuration and change the cycle time to something longer. IIS initially saves resources that are not used, so if the site was not requested after a while, it will actually free up memory for another application that will be used.
Brad christie
source share