If you are developing a Windows Store App using XAML (whether it’s C++, C#, or VB), there is a good chance there will be areas of your app where you would like to improve the performance. To assist with this, we’ve included the Visual Studio CPU profiler in all SKUs of Visual Studio capable of developing Windows Store Apps (this means we’ve moved the CPU profiler from being a Visual Studio Premium feature,
By: Andy Lewis and Matthew Mitrik
Today we’re here to help you:
Specify how you identify yourself on the changes you commit
Specify the default location for Git repositories
Use images (from either TFS or Gravatar) to identify authors of commits
Use a .gitignore file to block clutter from entering your user experience and your repository
Use the .gitattributes file to make sure changes are correctly recognized by the system
Modify Git settings from the command prompt
Got the latest version of Visual Studio with Git?
At various events, including TechEd 2012, Gregg and I have talked on customizing the Agile Planning Tools. The talk shows you can customize to Agile Planning Tools to fit any process, and to prove that we have created a Process Template that is completely different from anything we ship.
One of the areas that we have improved in VS2012 updates is dump debugging. In this post, I will explain dump debugging feature specific to the ARM architecture. We want to enable all developers who are building Windows Store applications targeting the Surface RT and other ARM devices.
First off – sorry that you reached this page and are not able to easily find what you need.
When you reach this page, it doesn’t necessarily mean that the feature is no longer supported or that content is not available for it.
A common pain point for today’s development teams is procuring and testing the plethora of devices modern applications are now running on. To ensure the highest quality for their business-critical mobile apps, development teams require robust mobile testing solutions that address the complexities of multi-platform development in a highly fragmented mobile market.
We introduced extended support in Coded UI Test for Cross Browser Testing with VS 2012 Update 2 February CTP (see this, this and this post for details). This post addresses details specific to managing browser profiles when using cross-browser testing feature.
In Visual Studio 2012 RTM, there was limited support for mixed managed and native debugging of Windows Store apps. This support was greatly enhanced in Update 1.
Enabling mixed mode debugging is simple. All you need to do is select your project and choose “Properties”
(2013 Mar 3 – Updating the work around steps. Also, when Update 2 RC is available, you can always install that to fix your problem)
For those of you installing the VS Update 2 – CTP3, there is an installation sequence that will put the web access work item tracking in a state where editing work items displays this error:
One of the top asks from people in the field is to have the ability to have a dropdown in which you can select multiple values. Few people know that there is already a solution out on CodePlex, although it has its limitation.