Well, I successfully deployed Planet Wrox to my hosting provider following pretty much according to 'exactly' your precise directions. I will make the following comments for those who may have the same 'mental blocks' I had and a comment about Visual Studio 2013.
1 - I didn't initially understand you could substitute an IP address anywhere a server name was requested; perhaps simple, but a mental block none the less. That made all the difference for connecting through the SSMS (SQL Server Management Studio). Thanks for that simple teaching.
2 - That same IP address technique worked just fine in my web.config "connection strings" as well. I suppose there's a disadvantage if they move the server.
3 - Even though I deleted the 'CREATE DATABASE' command created by SSMS in the .sql script file, my provider also gave me an error with what had became the new first line of the script, ALTER DATABASE [PlanetWrox] SET COMPATIBILITY_LEVEL = 110, which apparently sets the overall version of SQL Server to 2008, or 2012, etc. I didn't have permission for that command. But after my initial concern, I found the rest of the script ran just fine and all the tables were created and loaded.
A few observations:
1 - The impact of memory caching was really evident once the website was deployed. There were incredible differences in load times once a page had been accessed once. I imagine there's a load improvement once the page is simply built for the first time, but you could really see it in the picture loads - that's cache, not building, yes?.
2 - Visual Studio 2013 worked just fine for the entire book. I do have a remaining question about bundling and minification, but I don't think it's related to VS 2013.
3 - I feel like I passed a Final Exam at university today!
As I mentioned I'll have some additional questions (of course) that I will post in different threads. But what a great end to the journey that began with "Introduction, Who This Book If For"... Me!