11 Jan 2010
11 Feb 2011
Link to this post
I don't know how you have things setup or if you have some weird settings in TFS (or, if you are somehow taking a different path than me), but following your steps as I understand them will not get you completely to where you need to go.
You have your Sitefinity 4.0 web app project...
You add the entire project to TFS source control (including the config files).
You then EXLCUDE the config files FROM THE PROJECT.
*** This is where I run into problems....
When I EXCLUDE the files from the PROJECT, it wants to DELETE them from source control. Well, I NEED them in source control, because when the next developer comes along to develop, he needs to retrieve the full project INCLUDING the config files.
So, at this point, I have my config files on disk in the right folder structure (NOT included in the project), but NOT in TFS.
So... what to do?
I manually moved the config files into TFS source control.
Great, now they are in TFS. I BELIEVE this is what you were trying to get at CORRECT?? If not, please explain. And, if you were able to take a different route than what I explained, please let us know because with default settings for TFS source control and VS 2010, this is how it happened.
However, we aren't done yet...
Not sure if you forgot to mention or what... but, if you try to run the project at this point you have problems. Specifically, you have issues with the SecuityConfig file and access being denied to it. I'm pretty sure this is because of the READ-ONLY attribute that is now applied to our config files because we have them in TFS.
The only thing I can think of here is to manually go out and remove the READ-ONLY attribute from all those config files on disk. Is that correct?
Is all this the best way to handle a multiple developer scenario with TFS/souce control??
I would love Telerik or anybody else's opinions....