Visual Studio ALM Ranger Solutions
| NOTICE: 2013-05-16 This page has been retired! Please refer to https://aka.ms/vsarsolutions in future. |
Visual Studio 2012 | Visual Studio 2010 | Visual Studio 2008 | Visual Studio 2005 | Project Codes
More Resources to Explore |
    |
Visual Studio 2012 |
 |
Tooling |  |
Samples |  |
Guidance |
Use the Rangers ALM Assessment to find out pragmatically where your organization stands in case of ALM Best Practices by using the assessment questions and qualitative discussions. Based on the results, make an action plan for improvements.
Provides a master catalogue (treasure map) of the available ALM Readiness content to guide us through the process of becoming proficient in ALM practices. Get the paper based map and sample source code from CodePlex and the application from the Store:
The Build Release and Deploy (BRD) Lite is a set of build process reference templates that allows you to quickly setup a real-world build process in your environment. Also see Team Foundation Build Customization Guide for guidance.
Offers teams that are new to Kanban and teams that are using a manual, paper-based Kanban board, guidance and tool support for Kanban in Team Foundation Server 2010 and Team Foundation Server 2012.
The Visual Studio ALM Rangers Ruck process evolved and used by the geographically dispersed and virtual ALM Rangers project teams.
Includes hands-on lab guidance for the customization, deployment of Team Foundation Build. Also see BRDLite Reference Templates and Guide for reference templates.
Guidance and tooling to support scenarios for test case and test plan release management, including reporting and base-lining: sprint to sprint, release to release, and moving a feature through the branching guidelines scenarios.
Practical guidance for the implementation and disaster recovery planning for Team Foundation Server.
Practical guidance for Work Item Tracking (WIT) and Process Template customizations.
Upgrade scenarios and post-upgrade issues for Team Foundation Server and associated technologies. |
The Team Foundation Server Word Add-in allows you to import work items from a Team Foundation Server Team Project and generate professional-looking Word document from TFS Work items
Whitepapers and articles on using the Team Foundation Service built on Windows Azure, and its use by the Visual Studio ALM Rangers.
Common definition of personas and scenarios used in Visual Studio ALM Rangers guidance.
Guidance and a reference implementation of a software solution that automates the creation of Microsoft environments, in particular Visual Studio and Team Foundation Server.
Focuses on modeling tools and includes understanding and reverse engineering an existing application or starting a new application from scratch.
Practical guidance and tooling for the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.
Practical guidance for Visual Studio Lab Management, backed by VM Factory Guide automation.
An overview of Visual Studio and Team Foundation Server in the form of compact, quick reference sheets. Users who are unfamiliar with Visual Studio get a “quick” overview of features, value and associated Rangers guidance.
Practical guidance for branching and merging strategies on Team Foundation Server. Also refer to the Ranger Quick Response Sample Solutions if you have a need to implement a consistent branching model as part of team project or team creation process, that complies with this guidance.
A range of test tooling (Microsoft Test Manager, Coded UI, Fakes and IntelliTrace) practical and scenario based guidance.
|
![image[6]](https://msdntnarchive.z22.web.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/18/52/metablogapi/6646.image6_7F2ACA15.png "image[6]"){kind=small}
Visual Studio 2010
Visual Studio Coded UI Microsoft Word Plug-in Guidance and tooling for the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents. Guidance for the planning, setup, configuration and usage of Visual Studio Lab Management, backed by custom VM Template automation for reference environments. Team Foundation Build Customization Guide Hands-on lab guidance for the customization and deployment of Team Foundation Build 2010 activities such as versioning, code signing, and branching. Team Foundation Server 2010 Monitoring Management Pack The Team Foundation Server 2010 Monitoring Management Pack delivers the capabilities for professional monitoring and management of Team Foundation Server 2010 infrastructure components. Team Foundation Server Word Add-In The Team Foundation Server Word Add-in allows you to import work items from a Team Foundation Server Team Project and generate professional-looking Word document from TFS Work items. Team Foundation Server 2010 Upgrade Guidance This project addresses the broad topic of migration and focuses especially on process template, reports, and Enhanced TFS Management. Visual Studio 2010 Database Guide Practical guidance for Visual Studio 2010 database projects. Visual Studio 2010 Architecture Tooling Guidance Practical guidance for Visual Studio 2010 Ultimate, focused on modelling tools. Visual Studio 2010 Quick Reference Guidance Compact guidance for the field to cover Team System and TFS capabilities. This project addresses the broad topic of migration and focuses especially on process template, reports, and Enhanced TFS Management. |
Visual Studio TFS Branching Guide 2010 This Ranger solution focuses on applied and practical examples of branching that you can use right now. The 2010 release includes discussions around branching concepts and strategies but also focuses on practical hands-on labs. TFS 2010 Requirements Management The 2008 version was about general requirements management best practices and the best you can do with our current tooling to support these best practices. The 2010 is part 2 of this Ranger guidance focusing on new features of 2010 and how these features deliver better support for our RM best practices. Visual Studio 2010 and Team Foundation Server 2010 Virtualization Guidance for best recommendations for deployment of VSTS and TFS in virtual environments. The TFS Integration Platform is a project that facilitates the development of tools that integrate TFS with other systems. Also see TOC blog. Visual Studio Performance Testing Quick Reference Guide Practical guidance for Visual Studio Team Test. One single PDF file that includes topic areas such as setup considerations, load test results store information, test customization, and more. This tool takes a WCF trace file and a WCF client proxy, or a WCF interface contract, and generates a unit test that replays the same sequence of calls found in the trace file. The code generated is easily modifiable so that data variation can be introduced for the purpose of doing performance testing. |
Visual Studio 2008
Sharepoint Server Custom Application Development: Document Workflow Management Project Read about the real-world design, construction, and deployment of a custom SharePoint Server 2007 application to a mid-market enterprise customer using Team Foundation Server as an ALM platform. Solution and Authored Artifact Development Models for SharePoint Products and Technologies Learn to reconcile differences between artifact development and assembly development by combining components into a single version control repository, such as Visual Studio 2008 Team Foundation Server. This tool takes a SQL Profiler trace file and generates a unit test that replays the same sequence of database calls found in the trace file. The unit test is designed to be used in a Visual Studio Load Test. The code generated is easily modifiable so that data variation can be introduced for the purpose of doing performance testing. |
Team Foundation Server 2008 Branching Guide 2.0 Practical guidance around branching and merging with Team Foundation Server 2008. The package includes guidance, scenarios, Q&A's, drawings, labs and lab files. You can also download guidance for Team Foundation Server 2005. Using TFS to Develop Custom Sharepoint Products and Technologies Applications Use Microsoft Visual Studio 2008 Team Foundation Server to support SharePoint application development, and provide an integrated development environment and single source code repository for process activities, integrated progress reporting, and team roles. |
Visual Studio 2005
Operations Guidance for Team Foundation Server You can manage your deployment of Microsoft Visual Studio 2005 Team Foundation Server more effectively if you create your own operations plan. As you create your plan, you should understand key elements of the architecture of Team Foundation Server and how your deployment topology affects operations. This white paper explains those elements in detail, so that you can avoid common problems with your deployment. |
Project Server 2007 VSTS Connector The Visual Studio Team System Project Server 2007 Connector is designed to integrate the project management capabilities of VSTS with Project Server 2007. It's been developed by the Visual Studio Team System Rangers in response to significant customer demand for a connector solution. |
Project Codes
vsarAlmAssessment
vsarAlmExams
Not yet published
vsarArchitectGuide
vsarBranchingGuide
vsarBuildGuide
vsarBuildGuide
vsarCodedUIWord
vsarDeviceTest
Not yet published
vsarDevOps
Not yet published
vsarDevOpsPnP
Not yet published
vsarGuidance
vsarGuidance - QR
vsarKanbanGuide
vsarKinectBoard
Internal prototype
vsarLabMan
vsarLabMan
vsarPlanningGuide
vsarQuickGuide
vsarReportGuide
Not yet published
vsarSupport
Internal support projects
vsarTestReleaseGuide
vsarTestToolingGuide
vsarTfsPtGuide
vsarTiP
vsarTreasureMap
vsarUnitTestFx
Not yet published
vsarUpgradeGuide
vsarVMDemoSetup
Not yet published
vsarVMFactory
vsarWord4TFS
Comments
- Anonymous
October 03, 2012
Thanks to Rangers' tutorials, papers, and Powerpoints, and my encouragement, my group recently started using TFS. Following your tutorials, we are using branching (underway) and merging (in the early stages). At the same time, our main project is up to 27 projects of source code, and has grown fragile and difficult to install. There's really no reason to compile all that source code everytime, either. We want to move more fully to referencing .dll's instead, but I want to get it right the first time, so I seek your wisdom. In the Ranger's tutorials, I observed that you included folders /MAIN/Src, /MAIN/Docs, and /MAIN/Bin. The use of /MAIN/Src is obvious, but I have questions about how you use /MAIN/Bin. Other than including it as a folder your tutorials did not use it.
- When you compile, do you use a post-build event to copy the .dll to /MAIN/Bin (or /DEV3/Bin if you happen to be in that branch)?
- Do you have /MAIN/Bin/Debug and /MAIN/Bin/Release, or do you simply have /MAIN/Bin/*.dll which means the last version in wins?
- If you use /MAIN/Bin/Debug and /MAIN/Bin/Release, do other projects reference the specific dll of interest, or is referencing smart enough to reference the correct version according to that project's version?
- We are on VS2010, TFS 2010 and Framework 4.0. I want to move up ASAP, of course. Do VS2012, TFS 2012 and Framework 4.5 affect the answers to the above in anyway? Any other thoughts you may have or references that come to mind would be helpful. Might you have tutorials that make active use of /MAIN/Bin, for example? Don S.
- Anonymous
October 04, 2012
DonStuber, I recommend that you start a discussion thread on vsarbranchingguide.codeplex.com/discussions so that the team can start addressing your branching questions and focus on your "fragile" and "compile everything" points.