You're Doing It Wrong - I got on a conference call for our latest software release. The new project manager asked the test team to verify a bunch of tickets. A bunch came out fai...
The way it works is that you have one solution with with multiple projects in it. Two of the projects are for Windows Phone and Windows 8.1. The other is a shared project. The shared project name ends with shproj. The shared project is like a library and does not output a package. It also cannot be the startup project in Visual Studio.
There are a host of technologies in the Azure world to help you serve up web sites. They got the database covered with Azure SQL Database. It is a cloud based database. But it support relational queries. Deep down underneath there is a SQL Server Database there.
They have a separate Azure Blob Storage to deal with storing of files. That feels like a different idea to me, as I normally just stick blobs in my Oracle database. Then again, I deal with a user base on the order of 1000 or so. Blob Storage has its own set of ideas such as accounts and containers.
Next up we got Azure Queue Storage. I have also see it referred to as Azure Storage Queue. This is the standard queuing idea where you store a bunch of messages that will later be worked asynchonously.
Microsoft has the Azure Traffic Manager to direct users to destinations of choice. This lets you use multiple sites to serve up your web pages. And you can do an upgrade while keeping your systems and sites online.
Finally I want to mention Web Jobs. This is the Azure way to run background tasks. They can be regularly scheduled tasks. Web Jobs has its own SDK that you will want to become familiar with. So much to learn.