Hi. My team is new to Sitefinity development. We have set up a website app in Sitefinity 4.2 and we are usingTFS 2010 SP2 for souce code control, and configured everything successfully. I have set up a build controller against my dev teams project collection and we have started coding in our Sitefinity project against Work Items from this TFS collection.
The team is small, 3 developers so our TFS configuration is basic, built for a small dev team. We are writing custom modules and web controls for this app in C#. Each developer has been getting the project out of TFS, working locally to develop their custom modules and controls, and now have reached the stage where we need to deploy this code, first to our shared development environment, and then we need to move it to the Staging (test) environment. Because Sitefinity content is stored in SQL server, I have seen how it will write many tables in the backend in response to, for example, creating pages in the front end, and how it writes rows in several tables for each page or content item.
Is it possible to use the TFS build controller to make builds of our Sitefinity project and deploy out through our enviroments? Is there any way of combining SQL server changes - these would be schema and data changes and we would want to deploy differential changes only, not over-writing the destination SQL db if possible, so we could give our business users access to the staging environment to begin adding content there, and at the same time push new changes from the dev environment.
How should I do this? I tried queuing a TFS build against the Sitefinity project, and it errored saying there was no .sln file in the build folder, and complained about a missing Binaries directory, again in the build folder. In any case, this TFS build would only be managing the code and asp pages, I haven't even tried building the SQL changes.
How do other people manage their different environments? (dev/staging/live). I would really like to get TFS deployment working with Sitefinity