Visual Studio Team Services (formerly Visual Studio Online) and Team Foundation Services 2015 supports a cross-platform build system that allows you to easily configure builds that run on Windows, Linux, and even OSX. Visual Studio Team Services comes with a cloud hosted build agent that runs on Windows and iOS apps can be built either by integrating your own Mac or using MacinCloud’s VS Team Services build agent plan.
Update: A new blog post with a full fledged UI to support the below scenario can be found here – Performance testing with App Service Continuous Deployment
Back in September, we introduced a capability of Performance/Load testing with App Service Plan.
Leveraging Donovan’s great DevOps series on building his Ignite Demo here is a walk through for using Selenium with Visual Studio Team Services and the PartsUnlimited sample found at: https://github.com/Microsoft/PartsUnlimited
Getting Started with Selenium in a Continuous Integration Pipeline
Performing user interface testing as part of the build process is a great way of detecting unexpected changes and need not be difficult.
In Visual Studio 2015 Update 1, we enhanced the Git experience based on your feedback. As I mentioned in the most recent Git Futures post, there’s a lot more on the way.
No matter what you’re doing in VS, you usually want to know what repo you’re in,
In Visual Studio 2015 we are piloting a recurring and cumulative servicing update that provides fixes to high-impact bugs between our regular updates.
In the second servicing update recently made available, we fixed an issue in Visual Studio 2015 Update 1 that can cause Visual Studio to crash sometime after editing C# or Visual Basic files while debugging.
This blog assumes that you have a prior understand of functional testing with Coded UI Test on Windows Store. If not, please go through the introduction blog for Windows Store Apps. Here I would cover troubleshooting issues with the XamlWindow.Launch() API that has been explained in detail here.
Code Review with pull request is a central part of every git developer’s inner loop. Over the past few months, we’ve added a number of improvements to the pull request web experience for Visual Studio Team Services (VSTS), all focused on improving productivity while using pull requests.
At Connect() we announced the Public Preview of Visual Studio Marketplace – the one place to discover and acquire extensions, integrations and subscriptions for the Visual Studio family of products.
On Jan 10th, in just about 52 days, we hit a major milestone –
In Team Foundation Server 2015 we introduced identity fields which made significant changes to how the Work Item Tracking (WIT) system handles identity values. These changes help modernize the underlying system and provide support for upcoming features . However, the changes result in API and data format differences that TFS users (especially those writing third-party tools with ClientOM or REST) need to be aware of.
NOTE: An updated roadmap as of June 2016 is now available.
Last month, we released our first major milestone for process customization – the ability to add a field and modify layout, checkout my blog post on the topic if you haven’t seen it yet.