Team Coherence with Visual Studio 2010 - version-control

For source control we currently use Team Coherence 7.1.3.25, which has been working great under a few different editions of Visual Studio, the latest being VS2008. We are migrating to VS2010 and I am not sure how to get TC to work with it. Do we need to make the switch to TFS, or is there an option to get TC to work with VS 2010?

And here is the answer:
"Make sure that you check the 'SCC API' support option in the IDE Installation tool (IDEInst.exe in the installation folder).
When you next run VS, you should then have the 'Source Control' option under the File menu.
If you need more information, let me know.
Regards
Ewan McNab
Quality Software Components Ltd
Version Control with Team Coherence"

Related

What does "Visual Studio Code" setup uses?

I recently installed Microsoft new "Visual Studio Code" on Windows. The entire setup was quick and nice. What technology is that? Is it clickonce? It was smooth and quick
It's using Squirrel to create a self extracting zip archive containing a nuget package. Squirrel only supports per-user installation and because of that it doesn't impress me.
Enterprises want per-machine installations with auto-update disabled so that change can be centrally managed. Technologies like Click Once and Squirrel just ignore this and do limited things in the per-user context with auto updates enabled. Two different animals.

using NuGet with Visual Studio 2005

What would be the most frictionless workflow for working with NuGet and Visual Studio 2005? Is this at all possible? I understand that the plugin is only available for Visual Studio 2010, but there is still the package manager console wich seems to be nothing more than powershell. Can I run the console without Visual Studio and can the console download and integrate packages into visual studio 2005 projects? If so, how is this done?
Scott Hanselman blogged about adding NuGet "support" to Visual Studio 2008. You can probably adapt this slightly to work in Visual Studio 2005 too, though of course you won't get the same experience as in Visual Studio 2010.
Well, not really. A better title would be "How to Cobble Together
NuGet Support for Visual Studio 2008 with External Tools and a
Prayer." The point is, there are lots of folks using Visual Studio
2008 who would like NuGet support. I'm exploring this area and there's
a half-dozen ways to make it happen, some difficult and some less so.
The idea would be to enable some things with minimal effort. It'll be
interesting to see if there are folks in the community who think this
is important enough to actually make it happen. Of course, the easiest
thing is to just use 2010 as it sill supports .NET 2.0, 3.0, 3.5, and
4, but not everyone can upgrade.
Someone could:
Backport the existing NuGet Package References dialog to 2008 using
that version's native extensions (not VSiX)
Create MEF (Managed
Extensibility Framework) plugins for the nuget.exe command-line to
update the references in a vbproj or csproj
Use PowerShell scripts and
batch files to get the most basic stuff working (get a package and
update references.)
Maybe write a shim to get DTE automation
working...
But that's coulds and maybes. Let's talk about the MacGyver
solution. more ยป

IBM's RTC and Microsoft's TFS 2010

What in your view are the most important differences?
Need to make an expensive decision...
Information:
We have both Java and .NET Projects (few more .NET)
Very interested in project life cycle management.
Migrating from ClearCase
Both TFS and RTC are CRRM integrated to development environment (Visual Studio or Eclipse): they provide:
Change Management (CM)
VCS (Version control system)
Release Management (RM)
The difference is mainly in their architecture, where:
TFS provides a server SDK for facilitating integration with Visual Studio
RTC is build on top of an open-source application HUB able to aggregate any kind of tools (RTC baing the IBM Rational commercial implementation of Jazz)
The challenge in both CRRM tools is to manage the necessary bridge you will have to setup for various legacy tools (like an existing ticket system for instance).
Stay away from Accurev, it is a nightmare, as a developer with personal daily battles with it. Git, Mercurial, Darcs, or SVN are much better choices. As far as all of the "features" of Accurev, you likely won't ever miss them, you'll be too busy swearing.
RTC is Visual Studio friendly, and TFS is Eclipse friendly:
(RTC visual studio integration listed here)
https://jazz.net/downloads/rational-team-concert/releases/3.0
(TFS eclipse integration detailed here)
http://teamprise.com/ (purchased and renamed by MS)
I'd personally rather work with TFS, and I write integrations with version control systems for a living, and have touched both of these systems in a deep way. Ask if you want the details.
If you have a choice in the matter, go with Mercurial. Git is fantastic, but I found the Windows experience lacking. Get a separate bug tracker.
If you have a choice but must have version control integrated tightly with tickets, try http://fossil-scm.org/ - far less pain than either TFS or RTC to setup and maintain, though the IDE integration simply does not exist. But it competes solidly on core features with them in about 1 megabyte of download.
TFS doesnt have any support for eclipse or any such editors yet, (they are about to come, but no news yet). So which editor you use for your java projects that matters here. But Microsoft is coming up with teamprise which can let you connect TFS (which can work better for your java+.net)
And ofcourse for .net projects, TFS is the best, eclipse support for .net/c# is bad, we are using TFS and am lot happy with 2010.
I think for RTC dont know how much support is there for .net editors (VS or any other you prefer) but with TFS, you can certainly make .NET project work great and you can find Teamprise + TFS to work with eclipse also.
Is it really a question? Not nagging, but what is your toolstack to start with. What versions we talk about? (note Visual Studio 2010 and TFS 2010 are just around the corners - both a lot better, still usable for .NET 2.0 upward).
Without more information you get tons of idiotic little feature lists - because we dont know how to answer properly in the big picture. This is like "what are all the differences between a BMW 3 and a Mercedes SLK" - TONS of small things, TONS of relevant things, but what do you want? ;)

Integrating Diff Tools With Visual Studio 2003

I found a great article on integrating different diff and merge tools with Visual Studio 2005 and 2008: http://blogs.msdn.com/jmanning/articles/535573.aspx.
Does anyone know how I might integrate a tool like KDiff3 in the same way with Visual Studio.Net 2003? I would like to have KDiff3 be the default diff tool when I use the "Compare Versions..." menu item in the Solution Explorer.
For our source control, we're using Team System 2005, using the msscci provider to integrate.
What source control system are you using?
With certain systems you can specify what diff tool you'd like to use. Perforce has this...and I believe VisualSVN lets you choose what diff tool as well.
If you've got VSS...I think you're out of luck...
Thank you for that question and comment. It got me to realize the compare was coming from VS2005, even though I'm using VS2003, because the msscci provider I'm using for source control integration is the VS2005 version.
So, by going into VS2005 and using "Configure User Tools...", it forces 2003 to use the same tools.
I know that Devart CodeCompare shows good results on the integration with Visual Studio. But I don't know what VS versions are compatible with CodeCompare.

Source control for use with VisualStudio + Xcode?

I don't know much about source control beyond what I have used at work [Perforce]. I'm looking for a product with the following..
Free
Centralized (server running on the LAN)
Good integration with Microsoft Visual Studio (built-in / free plugin?)
Good integration with Apple Xcode (built-in / free plugin?)
Are there many that fit those criteria? What would you choose?
Thank you for any input.
Xcode has built-in support for SVN, CVS and Perforce.
Visual Studio has a plug-in for most source code control systems. A free one for svn is Ankhsvn
SVN sounds like your only option. I'd question why you think you need a centralised server, though.
Well subversion is the first one which comes in mind.
Ankhsvn/visual svn for visual studio
http://developer.apple.com/tools/subversionxcode.html for xcode