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
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.
Edited byTerrence_Tuesday, August 28, 2012 3:05 PM
To specify which solution you want to build you will need to set the Solution to Build property in the build definition editor to that solution. From that point we will deploy the first web application alphabetically in that solution. If you
have a specific web application you want to deploy you will need to create a solution with only that web application in it.
The setup wizard from the azure portal does it's best to set everything up for you based on some simply conventions of only 1 solution in your team project and only 1 website in your solution. This is something we expect to address in the future in
order to provide users with more flexibility and control.
Trevor, your reply is by no means a correct answer. Have you read Chris's post and my response? We are dealing with a more complicated issue than a walk trough of the feature with a simple TFS Project.
I am sorry our attempts to help you have not been... helpful. I hope that something in the following will address your question. If not, please reply with a detailed description of your team project\solution\project set up in TFService, and details
about your Azure account (what sorts of projects are you building, etc.) and we will try to assist further.
Well, I went back and setup a simple TFS project with one VS Solution with one website in it and that works.
There does not appear to be support for a real world solution where you have a TFS project with multiple vs solutions each with multple vs projects. There is no way to indicate which vs solution to target as the solution with the website that will
So I wouldn't mark it as "answered", I would post a message that says "we don't support this real world scenario yet" and then mark that as the answer.
Thank you, Terrence
Edited byTerrence_Monday, September 17, 2012 3:09 PM
what I'd like to see is some sort of (normal) TFS upload to Azure TFS (or pull/sync) which keeps EVERYTHING INTACT in terms of folders (and has the same look and feel as the folders section in Visual Studio (for both local and cloud TFS)
Now some time has passed - have you been able to resolve this?
I'm just hitting the same problem - I have just the one solution in a TFS project, but there are multiple website projects in there that I'd like to look at deploying - ideally to different Azure sites, that would be just great! Really a build definition needs
to have selectors for the path to use for deployment (writing that sounds so stupidly obvious, I'm wondering if it's been done by now... or we'd just missed it before) - surely that's possible?