Hey folks - just looking to bounce some ideas around about this - any feedback welcomed!
Scenario as follows:
1. My company has lots of web SITEs deployed
2. We are trying to integrate team foundation server (TFS) - version 2010 in our case - but will soon be upgrading (especially if it solves this upcoming issue i'm facing)
3. I'm struggling to follow the workflow on checking in web sites vs. web apps - don't see how web sites can be source controlled when the site files sit on a remote web server
Let me explain...web sites are the older way of creating .NET web applications and deploying them. Web sites are the more modern way of packaging and deploying a web application in .NET. I can clearly see the workflow for the web APP check in and deployment when using TFS in your workflow.
It seems very similar to check ins and deployments with winforms, console apps, etc. - no sweat.
With a web site project, you generally don't end up with centralized .sln or .proj files. Thus if you check in a web site from the server via visual studio and you open it again later - there is no "binding" to TFS essentially. You would have to have a local .sln file (perhaps it could be right with the web site, I'm not sure if that's a best practice though) to ensure if you open it, it is TFS "aware". But if another developer opens the same web site on the server, they won't get the same warnings, etc.
Finding this to be a real problem when trying to move from a "no source control" to a "source control" shop.
1. Wondering if I'm missing something awesome in TFS (either 2010 or the newer versions) that would help with this - for instance...was wondering if the git option in VS online would be helpful - i.e. check in the web site files right from the server this way.
2. Wondering if i need to convert all these web sites to web apps and if that is the only clear way to fix this issue...or perhaps i just copy all the web site files to the development machine in each case and use the "copy web site" for deployment...would have to put .sln files right with the web site files to do this though (as i mention in the text earlier here).
3. Had considered not using TFS for these web sites and just using SVN to source control the web site files with something like tortoiseSVN as a client (which i'm certain would work great but not achieve the TFS-first objective).
4. And finally...had read about SVN plugins for TFS, but unsure if that will just complicate things vs. just having VisualSVN doing point #3 right above.