Features under development
This feature list is a peek into our roadmap. It identifies some of the significant features we are currently working on and a rough timeframe for when you can expect to see them. It is not comprehensive but is intended to provide some visibility into key investments. Most features are linked to a blog post and/or UserVoice entry where you can learn more and comment. These features and dates are the current plans at this time and are subject to change. The “Planned Date” reflects when the feature will be available on VSTS and the “Server” column reflects when it will be available in TFS on-premises, if applicable.
Source: Team Services Feature Updates
From an email from Microsoft:
Invite stakeholders to a project to keep them informed on what’s happening with that team or project. They’ll have access to the team home page, where they can view updated project information. They’ll also have access to the backlog, taskboard, and Kanban board, where they can create and edit work items or work item queries. You can add unlimited stakeholders to your team projects at no charge – in addition to the five Visual Studio Online Basic users you get for free with your account!
If you intend to move existing team member(s) from existing plans to the new stakeholder plan, remember to visit the Microsoft Azure portal and remove any paid user plan that you no longer need, to avoid being charged for them on the next billing cycle.
With organizational accounts, users can use their own company credentials to sign in to Visual Studio Online. To use organizational accounts, link your Visual Studio Online account with Microsoft Azure and set up Azure Active Directory.
Looking for a nice tool to migrate an on premise TFS installation to a Visual Studio Online environment? Take a look at this new OpsHub migration tool.
Not to happy about it yet though…We getting some errors migrating source control files. Support is great so far…continuous delivering new versions, and getting better every week. Glad to be of help, in getting this product better and better…
If you have any questions about the tool, feel free to contact me, or comment below.
That is the question right?
Ever wondering when to get user licenses for TFS 2013? Sometimes it’s easier to check for when a license it’s not required. Copied the below out of the TFS 2013 licensing whitepaper from Microsoft.
Basically you can use a lot of the features if you have a MSDN Subscription. A Team Foundation Server CAL however is not required in the following scenarios:
- Entering work items through any interface, and viewing and editing work items you created. This enables users to enter and edit their own work items of any type.
- Accessing Team Foundation Server reports. Any read-only data that comes from the Team Foundation Server SQL data warehouse or is surfaced through SQL Server Analysis Services would be a report, but custom reports could also be written to call into Team Foundation Server APIs and could also join that data with other data sources.
- Accessing Team Foundation Server using Microsoft System Center Operations Manager. This enables operations staff to take operational issues encountered in production and raise them as issues to the development team, automatically creating a work item in Team Foundation Server.
- Accessing Team Foundation Server using the Feedback Client for TFS. This allows the user to provide Feedback about an application into Team Foundation Server.
- Viewing static data that has been manually distributed outside of Team Foundation Server.
- Up to two devices or users that only access Team Foundation Server to perform system administration, such as creating Team Projects or Project Collections.
- Up to five users when Team Foundation Server is purchased through the retail channel or for the free Team Foundation Server Express. However, a CAL is required for the 6th user and any subsequent user.
- Accessing Team Foundation Service via a Team Foundation Server 2013 Proxy. This enables Team Foundation Service subscribers with bandwidth latency issues to deploy Team Foundation Server 2013 Proxy to access the service
- Providing approvals to stages as part of the Release Management pipeline
Please be aware that this list might not be complete. And if you still aren’t sure please check out the full article here.
Recently discovered an excellent way to automate versioning of assemblies integrated in a TFS build definition. I followed the guide and instructions written at this code plex open source project
Then I created specific build templates including these options, so that creators and users of build definitions can edit all the versioning attributes a long side other customizations for two of our clients and they are very happy about it.
I really recommend this custom made build activities to all who need to automated assembly versioning included in their TFS build templates and definitions.
Good work guys!