How can I put my Borland C++ Builder 6 project into Visual Studio Team Services - tfs

We are putting our existing Embarcadero Borland C++ Builder 6 projects into the new free Microsoft source control called "Visual Studio Team Services" (aka online version of TFS or Team Foundation Server formerly called Team Foundation Service).
http://www.visualstudio.com/products/what-is-visual-studio-online-vs
How can I put my code from my BCB 6 project to use it with this system.
Of course I'd prefer to have IDE integration, but as long as I have some kind of GUI I'm fine with doing source code tasks outside of the BCB IDE.
Are there any BCB files that are binary and therefore might be an issue with comparing changes?
Any ideas are greatly appreciated.

C++Builder does not have any native TFS support (not even in the latest version), let alone any VSOnline support. At least with TFS, there are third-party plugins to let C++Builder access TFS:
SourceConneXion
TFS.us
For TFS, you can also use the standard TFS client GUI. For Visual Studio Team Services, who knows.
Several files are binary, including RES and TDS, but you usually don't need to do diffs on those. You should, however, make sure to set your DFM files to Text mode, as they are set to Binary by default. DFMs are always binary in the final executable's resources, but the DFM source files can be either text or binary, and you will likely do diffs on DFMs from time to time.

you could use the visual studio shell (aka 'team explorer everywhere') to do checkins etc
and you could also use the power tools (tfpt) to give you explorer integration.

Related

How to use Visual Studio Online source control with VFP 9 SP1

How can I use this Visual Studio Online source control with a visual foxpro (vfp) 9 sp1 project so that the VFP does automatic check in and check out as I change files and lets me undo or check in source code and view history like I can do in the Visual Studio 2010 IDE with dot net projects?
I see there's a free team explorer everywhere which i guess i can use outside of the vfp IDE - not sure how it will handle the SCX, FRX, LBX, PRJ files which are not textual.
May be you can't use VSO with Visual FoxPro 9, but surely you can use other SCM tools with Visual FoxPro, like SVN, Mercurial, PlasticSCM (which I use), etc.
For Diff and Merge you can use a new tool found on VFPx project, called FoxBin2Prg, that allow bidirectional conversion of VFP 9 binaries to text and vice-versa, so you even can modify the generated text version and rebuild the binary.
More info at FoxBin2Prg - Binary/Text Conversor for Microsoft Visual FoxPro 9.
Best regards!
I ran into this question while researching. Looks like Microsoft updated the MSSCCI to be used with Visual Foxpro
Install the Microsoft Visual Studio Team Foundation Server 2013&2015 MSSCCI Provider 32 bit : https://visualstudiogallery.msdn.microsoft.com/06c8e056-7f77-4a5c-9b8b-49318c143df8
It supports Visual FoxPro 9 SP2 connection to Visual Studio Online
Combined with the Team Explorer for Microsoft Visual Studio 2013, you can branch, forward integrate, reverse integrate. I'm still exploring it
You can't, and the main reason is that while PRG and other textual files are fine method code and other stuff is stored in DBF-format files, which your chosen source control software will treat as binary.

Referencing 3rd party components in Delphi 2005

I'm quite new to Delphi and I'm helping a team setting up a build server which are using Rad Studio 2005.
They have just bought DevExpress VCL and wants to use these. I would rather not have the component installed on the build server, but instead having them as a part of the source code and making sure that the project is using that version.
How is that done in Delphi?
We compiled all of our 3rd-party stuff into a BPL, then put that .bpl and corresponding .dcp and .dpr/.bdsproje into source control, so it gets delivered to the build server. Works well. In retrospect, it should have been a series of BPLs, divided by vendor, so that we could upgrade individual components/libraries without having to run regression tests on everything else.

Connecting TFS 2010 from Delphi XE

We are using Delphi XE at our company to develop some Delphi applications and as well as .Net.
TFS 2010 is our primarly source control mechanism for .Net; but we want to use TFS 2010 for Delphi.
I installed Team Explorer Everywhere 2010 but i couldn't see any menus or windows at Delphi XE editor about Team Explorer.
So how can we connect Delphi XE to TFS 2010?
AFAIK TEE 2010 is an Eclipse plug-in, Delphi is not an Eclilpse based IDE, nor it could use MSSCCI/SCC providers without adds-on. If TFS 2010 can work with an MSSCCI/SCC provider (you may have to install support separately), then you can use a Delphi add-on, see for example Use Team Foundation Server in Delphi 7?, it is for Delphi 7 but situation didn't change much.
Delphi XE can use a new API to handle VCS directly, but it is not compatible with older versions (making it less appealing for those who sell already existing add-ons), and thus requires someone to add TFS integration, and TFS is not usually the first choice by Delphi shops. Moreover fashion today dictates that DVCS are hot, and most efforts are in that direction.
You would need to find or produce a TFS 2010 plugin for the Delphi IDE! To the best of my knowledge, Embarcadero has only integrated SVN (Subversion) into the IDE (XE and XE2).
A quick Google search does not look too promising... so a lot of manual effort may be required on your part, or you may have to simply change your choice of source management solution.

Use Different versions of Visual Studio In Team Foundation Server

We have to use Team Foundation Server on different machines.
Our problem is in the .csproj files where we want to check in the changes made. The Team Foundation Server warns about resolve some conflicts about different versions. Now the question is that can we use different versions of Visual Studio on different machines on the same Team Project and how it would affect our development?
Being that the verison of Visual Studio being used is encoded into the .csproj file, it is difficult to use different versions of Visual Studio for the same C# (or other .NET) project. Since you can install different versions of Visual Studio side-by-side on the same machine (e.g. Visual Studio 2005, 2008, and 2010), it would be best to have everyone use the lowest common denominator (i.e. the newest version of Visual Studio that everyone has) for the project.
Hope this helps.

migrate a asp.net mvc solution file from 2010 back to 2008

i did an upgrade and it caused lots of problems. unfortunately i didn't back it up. Is there anyway i can convert a 2010 solution file back into asp.net mvc 2008?
Make a backup of what's left of what you currently have before doing this ...
Create a new solution in Visual Studio 2008. Create new projects for the 2008 solution. Use the project menu or right-click the project and choose "Add Existing Items..." Choose all the code files .cs .vb, etc from your 2010 structure and include them in the 2008 structure.
Basically you're copying all the code back into a 2008 structure with the 2008 formatted project and solution files. The code shouldn't be substantially changed beyond repair. You might have to manually address some issues in the converted code but once you know what they are it will be a repetitive process more than anything.
If you are writing code of any importance you should be using a version control system like as SVN. I haven't tried Visual Studio 2010 yet, but can tell you from experience that the differences between 2005 and 2008 are laughably small. You can down convert a 2008 solution file by manually changing the first two lines from:
Microsoft Visual Studio Solution File, Format Version 10.00
Visual Studio 2008
to
Microsoft Visual Studio Solution File, Format Version 9.00
Visual Studio 2005
the project files are fairly trivial as well with the product tag changing from:
9.0.21022
to
8.0.50727
Please note the changes I have listed for project files may not be 100% accurate and I have not tested for differences between service pack releases. However, creating a new project in an earlier version of Visual studio, making a copy and then doing an upgrade should allow you to run a diff and provide a better answer than what is currently accepted.

Resources