[EVENT] Materials Of The Event: Managing Projects With Visual Studio 2010 ALM
The Visual Studio 2010 Quick Reference Guidance project (vs2010quickref.codeplex.com) provides a quick reference poster to assist you with the planning of the new Team Project Collection feature, as well as Team Projects. Team Project Collections provide a more scalable deployment for TFS servers. One Team Project Collection in TFS 2010 is the rough equivalent of one TFS Server in TFS 2005 or TFS 2008. For more information on creating and managing Team Project Collections, refer to msdn.microsoft.com\library\dd236915.
[EVENT] Materials of the event: managing projects with Visual Studio 2010 ALM
The lack of centralized maintenance could hurt developer productivity in other ways. For example, this might be an unwieldy approach if your team is working on a large Microsoft SharePoint Online project that is developing custom solutions for multiple services (for example, the equivalents of , , , , , , and ) and deploying these solutions in multiple countries or regions. If you are developing on a computer that is running a client operating system in a corporate domain, each development computer would have its own name (and each local domain name would be different, such as 1 or ). If each developer is implementing custom functionalities for multiple services, you must use different port numbers to differentiate each service (for example, for and :81 for ). If all of your developers are using the same Visual Studio 2010 projects, the project debugging URL must be changed manually whenever a developer takes the latest version of a project from your source code repository. This would create a manual step that could hurt developer productivity, and it would also diminish the efficiency of any scripts that you have written for setting up development environments, because the individual environments are not standardized. Some form of centralization with virtualization is preferable for large enterprise development projects.
Since TFS 2010, Microsoft introduced a much more powerful concept of in-process event handlers. These type of event handlers that I had mentioned earlier, run out of process and so have limited access to objects on TFS. The new event handlers can access almost everything on TFS since they run in the process of TFS service itself. This has now become de-facto standard for creating event handlers on TFS. One can learn how to create such subscriber from a tutorial published by Martin Hinshelwood at -foundation-server-2010-event-handling-with-subscribers/. As Martin has mentioned in the tutorial, we are extending TFS by implementing the interface ISubscriber.
The Rational Team Concert Client (RTC) for Microsoft Visual Studio IDE is a team collaboration environment that brings the Jazz vision to .NET developers. With this flavor of the RTC Client, .NET developers can collaborate across teams, plan milestones and releases, track projects, manage source code and defects, and build from within Microsoft Visual Studio IDE. The RTC Client supports Microsoft Visual Studio versions 2005, 2008, 2010 and 2012.The RTC client is a first class integration into Microsoft Visual Studio IDE, enabling the .NET developer to use the power of Jazz from within a familiar environment.
Visual Studio 2010 comes with .NET Framework 4 and supports developing applications targeting Windows 7. It supports IBM Db2 and Oracle databases, in addition to Microsoft SQL Server. It has integrated support for developing Microsoft Silverlight applications, including an interactive designer. Visual Studio 2010 offers several tools to make parallel programming simpler: in addition to the Parallel Extensions for the .NET Framework and the Parallel Patterns Library for native code, Visual Studio 2010 includes tools for debugging parallel applications. The new tools allow the visualization of parallel Tasks and their runtime stacks. Tools for profiling parallel applications can be used for visualization of thread wait-times and thread migrations across processor cores. Intel and Microsoft have jointly pledged support for a new Concurrency Runtime in Visual Studio 2010and Intel has launched parallelism support in Parallel Studio as an add-on for Visual Studio.
Visual Studio Ultimate 2010 replaces Visual Studio 2008 Team Suite. It includes new modeling tools, such as the Architecture Explorer, which graphically displays projects and classes and the relationships between them.It supports UML activity diagram, component diagram, (logical) class diagram, sequence diagram, and use case diagram. Visual Studio Ultimate 2010 also includes Test Impact Analysis which provides hints on which test cases are impacted by modifications to the source code, without actually running the test cases. This speeds up testing by avoiding running unnecessary test cases.
Visual Studio Ultimate 2010 also includes a historical debugger for managed code called IntelliTrace. Unlike a traditional debugger that records only the currently active stack, IntelliTrace records all events, such as prior function calls, method parameters, events and exceptions. This allows the code execution to be rewound in case a breakpoint was not set where the error occurred. Debugging with IntelliTrace causes the application to run more slowly than debugging without it, and uses more memory as additional data needs to be recorded. Microsoft allows configuration of how much data should be recorded, in effect, allowing developers to balance the speed of execution and resource usage. The Lab Management component of Visual Studio Ultimate 2010 uses virtualization to create a similar execution environment for testers and developers. The virtual machines are tagged with checkpoints which can later be investigated for issues, as well as to reproduce the issue. Visual Studio Ultimate 2010 also includes the capability to record test runs that capture the specific state of the operating environment as well as the precise steps used to run the test. These steps can then be played back to reproduce issues.
The final release of Visual Studio 2013 became available for download on October 17, 2013, along with .NET 4.5.1. Visual Studio 2013 officially launched on November 13, 2013, at a virtual launch event keynoted by S. Somasegar and hosted on events.visualstudio.com. "Visual Studio 2013 Update 1" (Visual Studio 2013.1) was released on January 20, 2014.Visual Studio 2013.1 is a targeted update that addresses some key areas of customer feedback."Visual Studio 2013 Update 2" (Visual Studio 2013.2) was released on May 12, 2014.Visual Studio 2013 Update 3 was released on August 4, 2014. With this update, Visual Studio provides an option to disable the all-caps menus, which was introduced in VS2012."Visual Studio 2013 Update 4" (Visual Studio 2013.4) was released on November 12, 2014."Visual Studio 2013 Update 5" (Visual Studio 2013.5) was released on July 20, 2015.
On April 19, 2021, Microsoft announced Visual Studio 2022 (version 17). It is the first version to run as a 64-bit process allowing Visual Studio main process to access more than 4 GB of memory, preventing out-of-memory exceptions which could occur with large projects.