I installed TFS 2013 on my Windows server 2012 and I would like to transfer my projects from vss to tfs.
I downloaded the vss to tfs tool from [microsoft tool][1], but I was unable to install it because of compability mode, error message: "Windows Program Compatibility mode is on. Turn it off and then try Setup again"
According to this Buck Hodges blog post, you're not going to be able to do this in Windows Server 2012, and Microsoft isn't going to fix it. See the following comment:
... unfortunately, it is blocked in the installer. Right now we don't
have plans to re-release it, so you would need to run it on Win7-based
OS.
Incidentally, the post also addresses the question of upgrading to TFS 2013.
I would like to know if the upgrade tool will work with TFS 2013?
The documentation only mentions TFS 2010 and 2012. However, Hodges also addresses this:
... it should work with the caveat of what OS you install it on (see previous
comment).
the solution for me was : i installed the tool on another machine with win server 2008 , convert the projects and than move them to the tfs 2013
Related
I'm unable to connect TFS 2008 URL from VS2017; Is there any patch or providers needs to be installed
Googled alot about msscci provider,
but there isn't anything specific for 2017!
I keep a blogpost with the most up-to-date information on which versions of Visual Studio connect to what and which things you need to have installed. TFS 2008 has been out of support for a while now (April 2018) and Visual Studio 2017 can't connect to it anymore as a result. Team Explorer 2010 is the last version that officially supports connecting to this old TFS version.
In order to work with TFS 2008, you need Team Explorer 2010 or lower installed and use that for your interactions with TFS 2008. This does mean that you won't have any working Team Explorer or Source control integration in the Solution Explorer.
It's highly recommended to upgrade TFS 2008 to TFS 2018 or the soon to be released Azure DevOps Server 2019. Or, take away the maintenance burden of having to run your own servers, by migrating to Azure DevOps in the cloud. The process to migrate does require an intermediate upgrade to TFS 2018 though, so I'd start with that regardless.
What to download and install for:
Team Explorer 2010
Correct TE 2010 download location
Team Explorer 2008
I'm trying to import modified WITs to a existing project. But, It was showing the below error:
Microsoft.TeamFoundation.WorkItemTracking.Server.ProvisioningImportEventsCallback
Earlier it was working fine. But, now the issue started.
What could be the possible solution for this? I just wanted to upload WITs through Command prompt(witadmin.exe) only. Any hints/information would help
From your description, you are trying to use VS 2015 to connect to TFS 2017. Please check documentation Import, export, and manage work item types:
If you are connecting to TFS, you must use the same version of Visual
Studio or Team Explorer as TFS. For example, if you connect to a TFS
2017 instance, you must connect from Visual Studio 2017 or Team
Explorer 2017.
TFS 2018 and TFS 2017
Visual Studio 2017 or Team Explorer 2017 client:
%programfiles(x86)%\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
or, TeamExplorer, Professional or Enterprise in place of
Community, depending on the version you've installed.
You should install VS 2017 or Team Explorer 2017 to run this command. Although VS 2015 could run witadmin command against TFS 2017 sometimes, there would have unexpected issue.
However, I found the solution for this issue by myself.
Clear the Team Foundation cache from your server and the user system from the below path:
C:\Users\\AppData\Local\Microsoft\Team Foundation\7.0 (or 6.0)\cache
Delete everything from the cache folder and restart the server\system. Then Login to the server. Now, you won't get any error for uploading [WITs] using command prompt.
Follow the procedures as given in Microsoft Site.
https://learn.microsoft.com/en-us/vsts/work/customize/reference/witadmin/witadmin-import-export-manage-wits?view=tfs-2018
I have a question about in-place upgrading from Team Foundation Server 2010 to Team Foundation Server 2015
Our current situation contains the following software versions:
- Windows Server 2008 R2
- SQL Server 2008 R2
- Team foundation Server 2010
We would like to perform an in-place upgrade of this server to the following new versions.
- Windows Server 2012 R2
- SQL Server 2014
- Team Foundation Server 2015
It is a single server installation on a VMWare environment. Adding additional resources is not a problem. So for that reason we would like to go for an in-place upgrade.
With the information I found on https://msdn.microsoft.com/library/vs/alm/tfs/administer/requirements it does not seem to be possible with our current SQL version to upgrade to TFS 2015 in one go.
Should we first upgrade to TFS 2012 (which still supports SQL Server 2008 R2)? Then upgrade to SQL 2012 SP1, then TFS 2015..and so on.
Or should it be easier in our situation to migrate the TFS 2010 databases to an new server with all the latest versions and then upgrade the databases (and so not performing an in-place upgrade after all)?
There is a lot of documentation describing various migration scenario's so that is causing some confusion.
Can someone give us some suggestions or answer on what is the best way forward?
What you could do is:
Uninstall TFS from the current server
Uninstall SQL Server on the current server
Install SQL Server 2014 on it
Attach the databases to the SQL Server 2014
Install TFS 2015 and walk through the upgrade wizard.
It's sort of an in-place upgrade. Indeed be aware of the Sharepoint issue, it will be your pressing reason to make in in-between upgrade stop along the way, should you need it.
I see many client de-coupling Sharepoint from TFS anyway, as the Sharepoint functionality is rarely used, or even known.
Something else to consider. If you're using any of the sharepoint functionality in TFS 2010, and you want to keep the stuff stored there, then you'll probably want to upgrade to TFS 2012 anyway. TFS 2010 uses WSS 3.0 and TFS 2015 uses the latest version of sharepoint express. There is no direct migration from WSS 3.0 to the latest version so you'll need to use the bundled version in TFS 2012 as an intermediary upgrade.
If sharepoint isn't an issue then I'd suggest building out new infrastructure and migrating the TFS databases. This will be easier and IMHO has a couple of other benefits.
you can do a test migration to flush out any additional issues
get some timings so you know how long the real migration will take
This question of FxcopCmd vs Code Analysis has been discussed in SO, but my question is a bit more specific. We use VS2012 for development and TFS 2010 for TFS Builds. My question is - Without having VS2012 installed on TFS, I wanted to know if VS 2012 version of Team Tools (FxCopCmd) could be installed on TFS 2010 so that I get same FxCopCmd output on both development env with VS2012 and TFS build as well? Today when I run Code Analysis in VS2012, the count of violations obviously is different from the count seen with FxCopCmd run as part of TFS 2010 Build. This is understandable due to version differences, though I ensured that both run with the exact same command line parameters. FxCopCmd references point to v4.0 .NET assemblies in both cases.
Can I just have VS 2012 version of FxCopCmd or Team Tools installed on TFS 2010 and would that provide same results as that of running CodeAnalysis on VS2012? (Code Analysis in VS2012 in turn uses FxCopCmd)
Can I just have VS 2012 version of FxCopCmd or Team Tools installed on
TFS 2010 and would that provide same results as that of running
CodeAnalysis on VS2012? (Code Analysis in VS2012 in turn uses
FxCopCmd)
Yes, this is possible. You will need to specify a CodeAnalysisPath property value that points at the correct path, but otherwise the only concerns should be around licensing, not technical issues.
We've got a server with TFS2008 that we do all our builds on. I need to get an install of TFS2010 running. Can I run it on the same server (windows 2003) or do I need it on a seperate one?
This is not possible.
The exact question was asked before in the MSDN Forum and you can read all the answers here.
As Arun said TFS 2010 installer checks
if previous version of TFS is
installed on the computer and will not
let you install TFS 2010 if previous
version is detected.
There are many reasons why it is not possible to
install TFS 2008 and TFS 2010 side by
side. One of them is the fact that
both are creating an IIS web site with
the same name - "Team Foundation
Server".
Regards,
--Vladimir