A colleague has installed VS2008 Team Explorer (as part of his role in Scrum) and can successfully use Work Items, Documents and Reports. I now want him to use the TFS Source Control for non-code files (documents etc). He can successfully open Source Control Explorer but everything is greyed out as nothing has been mapped locally. Unfortunately, the "Map to Local Folder" option is missing from the context menus.
Is there another component he needs to install in order to use the Source Control part of TFS?
If he installs SP1 of Visual Studio 2008 he'll find it much easier to use. SP1 includes things like drag-drop into Source Control Explorer to add files, easier local folder mapping and links to open the local folder in windows explorer from the source control explorer.
You might also want him to install the TFS 2008 Power Tools - especially the Windows Shell Extensions (not selected by default in the installer) as they make it easier to deal with files outside of Visual Studio. This is very handy for word docs etc.
Related
I develop in PHP using Zend Studio - operating as an Eclipse plugin - has a really nice feature called "Automatic Upload" that can be configured on a per Project basis. This feature allows one to define a remote connection to a server for a Project, and also specify whether file copy to the remote server is "manual" or "on save".
We use the "on save" option extensively, as it allows us to edit a file via Eclipse, save it, and immediately see the file in play on our remote web server.
Specifically the functionality we are after is as follows:
Create or edit a local file in Eclipse
On Save of the local copy, automatically creates / updates the remote copy
On Delete of the local copy, deletes the remote copy
(cut/copy & paste behave in a conceptually equivalent way)
and
Manual batch "upload to remote" and "download from remote" menu options that allows full upload / download of all files as well as manual cherry picking of files to upload or download.
This feature is really nice and has very broad application so I expected it to be standard Eclipse functionality, however I have installed Eclipse Oxygen, and can't find it. I have subsequently done rather a lot of searching, and although there are some manual options that have appeared, the closest I can find to an automated copy equivalent is the Parallel Development Tools plug-in which provides a "Synchronized Project" option.
Synchronized Projects require git running on both local and remote and a git folder structure inserted into the Project. Additionally, hidden files are injected into every Project sub-folder.
The above renders Synchronized Projects too "heavy" and potentially problematic to manage for us.
So I am fairly desperately looking for an Eclipse Oxygen (or Neon is fine) plug-in that provides the functionality outlined above.
Your input is greatly welcomed. Thanks in advance!
While not exactly remote sync, a little lateral thinking has given me exactly what we need. What I did is as follows:
Remote (linux)
Install Samba
Use Samba to present the desired folder as a Windows share
Local (PC)
Windows File explorer
mapped the remote windows share to a local mapped drive
Eclipse
downloaded and installed the File Sync plug-in from Eclipse market place
right-clicked on my Project and selected Properties => File synchronisation, and configured the desired folders (setting the "remote" as the mapped drive)
and one final item (because we are mapping from a Windows local to a Linux remote) : Window => Preferences => General => Workspace Set "New text file line delimiter" to "Other => Unix"
And hey presto, everything is working 100%.
You can do this by a project builder Ant buildfile. Alternative, there are others build system that are implements the Eclipse project builder (to be executed on save), but which must be installed separately. You can also implement your own incremental project builder in Java.
We've updated to Visual Studio 2017 and switched to Team Services (VSTS) as our source control. I've migrated a few old projects and am using the Microsoft Installer Project extension to provide compatibility for the original setup projects.
However, there seems to be a potential issue with source control when working with the setup projects. Attempting to make any change results in the error:
The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out.
Modifying files of other projects within the solution work correctly and trigger checkout from the repository.
I have not been able to determine a way to properly check out the setup project and work with it under the new source control. I'm unsure if it's a bug with the extension or if it simply lacks support for VSTS.
Has anyone successfully been able to work with setup projects (.vdproj) in conjunction with VSTS? If not, is there a workaround?
Edit:
Image of context menu:
You can apply the following workaround, since it seems to be a bug in the installer extension:
Choose 'Open file in File explorer' in your context menu
Open the project file in your favorite texteditor
Make a dummy change (adding a space character in an empty spot is enough)
Visual studio will prompt to reload the project and has explicity checked out the project file.
see also here
I submit a feedback here: The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out
The workaround is that you can check out the project manually. (Right click the installer project > Check out for edit)
Is it possible to disable the automatic adding of new files to TFS in Eclipse without using the .tpignore configuration file? I would like to distinguish which file of a folder is added to TFS. For example the TFS plug-in tries to add the temporary file created when a version controlled excel sheet is opened. For me this is currently the biggest issue with the TFS Everywhere plug-in.
The most effective and convenient way is using the .tpignore file which in TFS 2010 and prior. In TFS 2012, with local workspaces, Visual Studio and the TFS plug-in for Eclipse have standardized on the new .tfignore file.
Possible duplicate with Do not automatically pend some additions in TFS plug-in for Eclipse .
The terminology used by most source control providers, including TFS,
is ignored.
You could also add the file format in the list defined files which are ignored in TFS by default.
To distinguish which file of a folder is added to TFS you could use some third-party tool such as TFS power tools, the file in TFS will have a green small arrow in the lower left corner of the file, just as the screenshot in my reply of this question.
I'm trying out the new Team Foundation Services and I'm wondering how people manage source control of non-VS-Project files. So my solution is added to the TFS source control, but if there's some Word Templates, Crystal Report files, etc that aren't part of the solution, but are supplementary to the application that need to be source controlled as well how would I go about doing that?
Thanks
Have you installed the Team Explorer into Visual Studio - I suspect you have.
Use Source Control Explorer to Manage Files under Version Control
Open Source Control Explorer
Do one of the following:
From the menu bar choose View, Other Windows, Source Control Explorer.
From Team Explorer, choose Home, and then choose Source Control Explorer.
Then in the Source Tree just right click and select Add Files.
See here for lots more info Working within Team Explorer
I'm developing a QNX app (thus I'm using an old version of Eclipse-CDT C++ etc.). Up until now I've been checking out with TFS and then importing the project files to the workspace via Import->General->ExistingProject; this means I can build/debug etc, but I've only had TFS functionality available via TeamExplorer from the TFS perspective. If I import the same projects to a different workspace via Import->Team->TFS then I have extra TEE functionality but I can't build/debug etc.
So, what's the recommended way to do this? I'd like both functionalities.
Edit ---
I imported each project one-at-a-time via Import->Team->TFS and it worked.
I'm not sure why importing from TFS doesn't detect that project's nature correctly. (Are you not checking in .project files? Are you using Maven?)
Regardless, if you want to go the route of importing an existing project from disk, just go to the Team menu, select Share, then select TFS. It should detect your working folder mappings and simply set TFS as the source control provider for that project, which should give you all the TFS bindings from within editors and views.