Well I appreciate your "tip" about reading the whole article.
Before I post a question online I do lots of searching for answers and of course I read the whole article. But to be sure I went back and picked up right where you sugggested after the line "At this point..." and re-read the whole article.
The article does not address my question.
Brian writes "As part of linking the accounts, we also created a continuous integration build definition that will build and deploy your app to Azure each time you check in. "
One of the many "VS solutions" that are in my "TFS Project" has a website project thats build definition is using the AzureContinuousDeployment.ll.xaml template. When I queue up a build it just builds it and puts it in the drops folder like it always
has.
The article and nothing I have read describes how to indicate what solution and then what website project will get deployed to that Azure website that just got linked.
I may have 3 websites, all of them can't deploy to that linked Azure website. So there must be some indication in the build definition that tells it to deploy to the Linked Azure website and not the drops folder.
Brian's article addresses an situation where the user has one VS web project that gets linked to Azure so it is a one to one. I have a many to one setup.
I am clearly missing something, and I am slow, so please spell it out for me.
Thanks, Terrence