Create managed continuous deployment pipelines to release quickly, easily, and often with Microsoft Release Management for Visual Studio Team Services (VSTS) and Team Foundation Server (TFS)
Your guide to configuring and customizing work tracking processes when connecting to Visual Studio Team Services (VSTS)
Your starting point in the use of Visual Studio Team System
Source: Visual Studio Team Services
Nieuws over customization van process templates!
A college of me pointed out this Scrum checklist created by Jeff Sutherland which is pretty nice: Click here
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.
Visual Studio 2013 Update 2 (Build 2014)
Today we are announcing the availability of Team Foundation Server 2013 Update 2 RTM, continuing to deliver on our commitment to bring on-going value to Application Lifecycle Management (ALM) developer tools through continuous releases of new features and by resolving known issues.
In addition, we are also making available the Release Candidates (with go-live license) of Visual Studio 2013 Update 2 RC. This release includes new features for creating apps targeting Windows Phone 8.1, the ability to build universal Windows Apps targeting the Windows Runtime, TypeScript 1.0 RTM, and many other new capabilities. In addition, Release Management Update 2 RC includes a new feature that enables tagging servers for easier deployments. For more information about using Visual Studio 2013 Update 2 RC in a production environment (go-live use), see the Statement of support in the Visual Studio Update KB Article.
Nice feature asking by a lot of customers finally added in TFS: You can configure non-working days, and these are excluded from burndown charts.
Full article from Microsoft: Visual Studio 2013 Update 2 (April Release).
Looking for and easy obfuscation solution for your .NET application?
I found the .Net Reactor tool very helpful in easy obfuscating some .Net assemblies and executables. The tool has a user interface but it can also be used with the command line. I created a post build event in a Windows application to obfuscate all assemblies. In this way all builds (local and TFS buildserver) obfuscate the assemblies in Release mode configuration. Below the description and features of the tool from the website.
What is .NET Reactor?
.NET Reactor is a powerful code protection and software licensing system for software written for the .NET Framework, and supports all languages that generate .NET assemblies. Its’ main features are : Continue reading “.Net Reactor Obfuscation”