Tfs 2013 Api: capacity and days off - api

I develop small project using tfs API. I have no problems with working with workItems,projects or teams but i'm wondering if is possible to get capacity and days off for specific team and specific iteration (within one project). It is possible to achive in TFS 2013 (or maybe in TFS 2015)?

You can use the Capacity REST Api of TFS2015

Related

Replace Code of TFS project in a server from a different Server

our team has migrated TFS projects to a new TFS server but few members of the team are committing code to old TFS server unknowingly. How do we migrate the code (Pull Requests, Branches)on the old TFS server and just replace the code part on the Target Server. Because, there are other items like user stories, TFS tickets valid on new server as users creating them.
Do we need to take down TFS server and will it affect other projects in collection.
I cannot find a straight forward way.
You can't find a straightforward way because there isn't one. The amount of effort that would be involved in re-synchronizing the two instances would be absolutely massive and would require the setup and usage of various third-party utilities.
Source code is easy enough to address on a person-by-person basis (have them update their remotes to point to the new server and push there instead). Pull requests? No way to migrate. Work items? Possible but a huge pain. Other stuff? Who knows.
Your best bet here is to cut your losses.

Limited to 100 result TFS api

I am using power shell to get data from TFS 2018 (on Premise)
I'm trying to fetch details of our releases using the TFS API.
I can't seem to return more than 100 entries whatever I try.
http://server/tfs/collection/project/_api/_apis/release/releases?api-version=4.0-preview&$top=500

What is the best approach to move a single project from tfs 2015 to tfs 2017 (different server)

I have 2 different tfs server setup , one runs with tfs 2015 other with tfs 2017.
I need to move a specific project from 2015 to the 2017 instance.
Please guide me with the best approach that we can go with...
You could not directly move things based on team project level , this seems like an inherent design issue with the source and work item entities. Since there is also not able to move a Team Project between Team Project Collections, there has been a uservoice:
Make it possible to move a Team Project between Team Project Collections
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2037613-make-it-possible-to-move-a-team-project-between-te
You have to move the entire team project collection if you want to keep all workitems, source control history for that specific project. If you just want code, the simplest way is copy them and add it in a newly created team project in TFS2017.

Microsoft Dynamics CRM Website

I had a genius idea today to try and create a website that would access our CRM database and will report on support cases.
The idea would be to have a page that would be visible in the office and members of the support team can view the current status of support cases.
I've downloaded the CRM SDK and I've read a couple of manuals, but I can't seem to find a decent starting point for a complete rookie..
Are there are good tutorials out there on how to create a website that will communicate with CRM's database, preferrably for a VB.NET application.
There are several products that implement your idea.
The most famous one is the Adxstudio, you can find a community edition (also for CRM 4.0) at this address:
http://community.adxstudio.com/products/adxstudio-portals/
After you can check the source code, but they use C#

Migration from SharePoint 2007 to SharePoint 2010

I am looking for a migration tool. We want to upgrade from SharePoint Server 2007 to SharePoint 2010 in a new environment. We need to have functionality to granulary select which content to migrate and eaven select to map to new structure in the new solution.
We want to tag the content migrated.
The migration tools we are considering are AvePoint, Axceler Davinci, Metalogix.
I'm doing migration scenarios for a consultant firm based in Montreal. First of all, I think you have the correct thinking about how you want to get this done. Doing a SharePoint upgrade (database upgrade) usually bring your SharePoint 2007 problems over to SharePoint 2010.
Here's what we usually do :
Define governance for the new SharePoint platform
Define the new Information Architecture
Implement the new Information Architecture (build sites, lists, libraries, etc.)
Migrate the content over
Tools such as Sharegate (www.share-gate.com) can allow you to do some mapping from your old content source over to the new one.
Hopefully, this will help you!