I have got 8 projects.
Projects referencing each other.
I exclude all dll files of my own projects from sourcecontrol
But every build the dlls gets changed and tfs enters into the conflict mode.
I want to avoid it.
is that possible ? And how ?
Thanks
PS: Tomorrow is my birthday this would be a great present
Delete those DLL's from TFS source control. Probably they are checked in once and now TFS will try to update them constantly when they change.
Related
While viewing the outgoing changes in Eclipse Team Synchronization(Subclipse), I am able to see the unversioned files also, like the generated class files, build folders, etc, which I do not want to see in this view. I dont want to add it to svn:ignore, since I have to do it manually for all the additional folders generated.
Is there any setting to change this to show only versioned files in this mode always?
Tortoise SVN client shows this option while committing, to show only versioned files. I am looking for such an option in Subclipse Team Synchronization view. Thanks in advance.
eclipse_outgoing_view
You should svn:ignore build folders.
Otherwise it's only a question of time until you or your colleague checks in the build folder
You should use svn:ignore, and note that once you do for a folder, all child folders are automatically ignored. In your example, if the build folder were ignored then everything inside it would automatically be ignored. It looks like your build folder has already been added to repository though, so maybe you can ignore the dist folder inside bin.
A while ago, I moved a large number of files into an new project to better organize my program. Now I have discovered that all history have disappeared since TFS (of course) solve it by removing the files from the old location and create new files in the new location.
My question is whether it is at all possible to restore the history for the files?
This can only be accomplished by using a migration tool like OpsHub or the TFS Migration Tools.
You will have to destroy the files in their current location, do the migration and then re-do the changes made since the migration. There is no way to check in the history "behind" already checked in files.
How badly do you need the history? And Could you live with the history being in the old project?
I have an application that is developed without any version control system so far, and I want to use TFS version control from now.
I have different copies (snapshots) of projects files stored at different times of project development and I want to store them in TFS repository too.
Can I use single workspace and copy each version to that workspace
and check in? Does the changes to all files captured automatically this way?
Where can I submit time and version history for each stored version?
So, you have the project in its current state and versions of it from previous dates?
From my experience, it's best to check-in the current version in Tfs as you would do for a new project. This becomes your working copy and all future changes are checked-in/checked-out and tracked in history.
For the pervious version, create an Archive folder in TFS with sub-folders for each date when you kept a copy of the project. Check in all files of that version into the appropriate folder. This can be used for reference.
I have several config files in different projects in my master solution that are set to "Copy if newer" that tfs build is not getting the latest for on each build.
I currently have the build configuration option "Clean Workspace" set to "All". I would think it would be copying the latest files from TFS but it is not. It is getting prior versions.
Furthermore the build folders on my local machine reflect the latest files from TFS. Is there a setting I am missing somewhere?
I managed to find the problem and it didn't have anything to do with TFS. I had multiple versions of the same config file in various projects within my solution.
To correct this I added a single configuration file at the solution level and added it as a linked file in all the projects where I needed it.
How to Share App.config?
We have a new ASP.NET project on VS 2008 environment, and a new TFS server was setup for it, but originally the bin folder of the project also got checked-in.
The team has about 10 active developers at a time and it a big issue now as some of the common libraries remains checked-out by someone or other.
As per the best practice, I now wish to fix this issue and remove the bin folder out of the version control AND I need to ensure that from now on, when a developer checks-in his project, the bin folder again does not gets checked-in. How do I ensure the both things with the correct approach? It would be great if I can do something as an TFS Admin so that from the next day all developers automatically get some settings pulled into their boxes so that they stop checking-in the bin folder once I have removed it from TFS control.
I am a beginner in TFS, as earlier I used SVN primarily, so please point me to the proper steps, documentation. Thanks!
Delete the bin folder in solution explorer, this will add a delete to the pending checkins.
A build should re-create the bin folder, but not add the folder to the project (and thus there'll be no prompting for it to be added to version control).
This won't prevent someone adding it (or anything it contains) back into version control outside of VS (eg. from the command line, or adding the bin folder back into a project). I don't think there is anything you can do to stop arbitrary files being added except training (if your developers cannot handle this, how do they handle all the other "don't do that"s associated with development?)
Updated, since this was written TFS (including VSTS and Visual Studio1) allow files and folders to be ignored via a .tfignore file.
1 Often Visual Studio does not pick up changes to the .tfignore file, needing a restart.