Within TFS Web Access 2012, when setting the capacity for the sprint, there is a button that says "Copy Capacity Information from the previous iteration". For one of our Team Projects, the button is disabled:
All other features of Web Access seem to work fine. This Team Project was created in TFS 2010 using the Agile template, and then migrated into TFS 2012. However, we have other Team Projects that are similar, and this button is enabled for them.
Does anyone know what is required for this button to be enabled?
In playing around with it some more, we discovered the problem. In order to enable that button, you have to have a previous sprint checked in the Team Project iterations setup.
Related
We’re running TFS 2013 Update 1 and I’m planning an upgrade to TFS 2015 Update 1.
We have both SharePoint and Reporting Services installed and configured for TFS that I like to remove, because nobody ever uses them.
So, do I simply uncheck both Reporting and SharePoint during the TFS 2015 upgrade wizard. Is this the best way to do it?
Or, do I un-configure Sharepoint and Reporting Services first from our TFS 2013 installation? If so, what are the steps to do so?
Environment:
Server computer A:
Application tier for TFS 2013 Update 1
Data tier: SQL Server 2012 SP 1 for the TFS databases, and Reporting Services databases
Sharepoint services (only for TFS)
Server computer B:
SQL Server 2008 R2 hosting the SharePoint databases.
You can do either.
I'd probably uninstall/disable first if you're really sure you don't want them in the future (check with all the teams that they're not storing docs in SharePoint as they will lose them). That way the backup will be smaller/faster when you backup before you upgrade (Make sure you take a backup!!).
It's simple enough to do, just fire up the TFS Administration Console.
Select Reporting, Edit (this will stop the jobs) and uncheck "Use Reporting". Click OK.
For SharePoint, click SharePoint Web Applications and under the top section, click Modify against your server connection and choose Remove.
Make sure you take a new backup at this stage and then you can start the upgrade.
Some things to consider:
Are you sure you want to do this in-place? You could clone the server to new hardware and test the upgrade first or perform a migration upgrade. It means less downtime in the event of something going pear shaped.
If your collection(s) are large, this is likely going to take a long time. The 2015 upgrade seems to be slower than previous upgrades due to all the schema changes.
Are you sticking with a single server? That's fine, but you won't need server B for SharePoint so you could move to a dual server TFS install if capacity is a problem (You'd need to upgrade the SQL version on server B to act as a data tier though)
I'm a couple years late, but this still popped up in a search result so worth mentioning - use cmd prompt to do this:
Navigate to %programfiles%\Microsoft Team Foundation Server %#%\Tools\, and type TfsConfig.exe setup /uninstall:SharePointExtensions . This will "unconfigure" the feature in your App Tier.
In the process of switching my folks over to TFS 2012, I was evaluating the team project reports I moved over. When I double-clicked on a report to open it, instead of seeing it in a tab within my VS 2012 IDE, it opens in a separate web browser window.
This behavior exhibits in migrated team projects (from 2010 to 2012), as well as newly created team projects. I'm inclined to think it's a configuration issue missed on my part, but I can't seem to nail it down.
[Migration details: upgrade performed by detaching 2010 collection, reattaching to running instance of TFS2012 on new hardware. ReportServer database was moved separately. Hardware is all WinSrv2008R2, SQL2012 Standard.]
UPDATE: altered title as this is happening to any/all settings and controls, as well, for any given team project (Security, Group Membership, Work Item Areas, etc). Anything that is URL-based. So, at least it's misbehaving consistently.
If I'm understanding you correctly, this is the expected behavior for TFS 2012. All of the controls you mentioned are part of Web Access and should be viewed/altered in a browser and not VS.
I wanted to know,
if, I can setup sharepoint 2010 server along with visual studio 2010. And sql-server on another machine in some domain
and
create multiple accounts on the sharepoint 2010 machine
and allow developers to develop sharepoint projects on the same machine with those accounts.
Also I wanted to know about version controls system like svn availability for sharepoint 2010.
in our company each developer has own development server, but some time we work simultaneously on the same server. I don't know why you need separate slq server, for development purposes SharePoint works fine with SQL express installed on the same machine. But if you wish you can use separate SQL server of course. If you would like to use specific accounts for SharePoint it is a good practice. Look at this post, there is some information about typical SharePoint accounts pool.
About simultaneous development. If you work with Visual Studio, not configuration, when you are deploying solutions server will restart IIS each time, is is not so useful for normal development of few employees. Also if you will decide to work like this, my advice to work in different web applications for each developer it will allow you more useful debug capabilities. You will not interrupt each other because of attaching to the same process w3wp. But notice, SharePoint is flexible and extendable environment, you can do I lot of things just with configuration and JavaScript development by SharePoint Designer. So if you will work most of time by configuring it will be possible successfully work on the same server for whole team.
About source control. If you are developing with Visual Studio, TFS is for you, or any other source control system, like svn or git. If you are develping by configuring with SharePoint Designer, I advice you to store some reusable functionality also withing TFS, by just copying. For other content you can turn on versioning on SharePoint libraries, so each your modification will be stored with comments if you wish.
I'm creating a CRM 2011 plug-in. I created it with the Visual Studio Solution Template for Dynamics 2011, and authored it as a CRM 2011 Plug-In Library. After completing the iniital implementation and testing in CRM, I now need to associate the plugin with a different Entity / Attribute / SDK Message. So...I re-opened VS to try to create another plug-in or to otherwise edit it this one.
Oddly, I get a WCF Error from Visual Studio's IDE when I re-start an existing SLN that used to work. Specifically, I get the error when I start the CRM Explorer in VS. The error is pretty generic -
The server was unable to process the request due to an internal error. etc .etc.
The CRM Explorer tree shows 0 Entities and 0 Option Sets after the error, though the other tree nodes seem to have the correct content. It feels to me that something in my Org or CRM Server has broken the VS integration, but don't have any idea what that might have been. I mean I hadn't made any changes to the Org at all in a week or so (though I did apply August Windows Updates!). I'm on Cum Update 8 at the moment.
When I delete the hidden blah.SUO and the blah.docstates.suo files, and restart VS ... the CRM Explorer prompts for my server / credentials / Org as expected for the initial start. However, I get the above WCF error again and the CRM Explorer does not populate correctly following this "reset". I have also tried uninstalling the CRM Developer Toolkit without luck.
Anyone seen this behavior before, or have any suggestions?
I have seen something like that happen when the WCF endpoints were re-configured (CRM Deployment Manager). You can check to see what the endpoints are in the Settings - Customizations - Developer Resources
I had a similar issue: trying to connect to CRM Server through development toolkit add-in to VS.
Resolution: add the user to the CRM Organisation and assign role "System Administrator".
I am in a situation where the corporation has just recently upgraded to TFS 2008. They have no intention of upgrading to TFS 2010 at this time. As a development group, we've moved to Visual Studio 2010 this week. As with any large corporation, we cannot get our own environment created to install TFS 2010. Steps on too many toes, and isn't corporate standard. Etc.
I want to take full advantage of the new testing features in relation to the new UI Testing and other features. This appears to require TFS 2010. So my "dream" is to do my daily work at the office and write tests, but at night, have my code synchronized with my TFS 2010 server at home and run automated builds with the full testing capabilities enabled.
So is there is best practice for this? I've read up on the Workspace theory and the binding issues that are involved and that sounds the biggest hurdle to overcome.
Possible Solution - Create two workspaces $/WorkProject and $/WorkProject-Mirror and use a custom application using FileSystemWatcher to kick off a job that synchronizes code changes and a custom rewrite of the bindings. Use job on work laptop and home machine to allow bi-directional binding.
Research to see if TFS Integration Platform will help with this
You are correct the new testing UI (Test Manager 2010) requires TFS 2010, you are also correct that you can use the TFS Integration Platform between a TFS2008 & TFS2010 server. Then use test manager on the 2010 server.
All the above should be easy, the tough part will be the bindings in the solution file. I would suggest you have a second one created that points to your TFS2010 server so that you can open the correct solution file for the correct environment without stepping on your co-workers toes.
I think the two workspace route is overkill, it's just a solution file you need.
I wonder if you could use a read-only account to perform a get from TFS2008 and then do a check-in to your TFS2010 with a more-privileged account. I'm sure those two things and a little clever PowerShell scripting could get you what you're looking for.
I would encourage you to write a second utility to monitor that this script continues to work and to notify you if it detects a failure or something.