View source for Microsoft Visual Studio

{{Use dmy dates|date=June 2017}}
{{Infobox software
| name                 = Microsoft Visual Studio
| logo                 = Visual Studio 2017 logo and wordmark.svg
| logo size            = frameless
| screenshot           = Visual Studio 2013 EN.png
| caption              = Screenshot of Visual Studio 2013, editing a program's [[C++]] source code
| developer            = [[Microsoft]]
| programming language = [[C++]] and [[C Sharp (programming language)|C#]]<ref>{{cite web|url=http://www.lextrait.com/Vincent/implementations.html |title=The Programming Languages Beacon, v10.0 |first=Vincent |last=Lextrait |date=January 2010 |accessdate=5 January 2010 |deadurl=yes |archiveurl=https://archive.is/20120530/http://www.lextrait.com/Vincent/implementations.html |archivedate=30 May 2012 |df= }}</ref>
| operating system     = {{Plainlist|
* [[Windows 7 SP1]] and later
* [[Windows Server 2008 R2 SP1]] and later<ref>{{cite web|title=Visual Studio 2015 System Requirements|url=https://www.visualstudio.com/en-us/productinfo/vs2015-sysrequirements-vs|website=visualstudio.com|publisher=[[Microsoft]]|accessdate=10 November 2014}}</ref>
  }}
| language             = Chinese, Czech, English, French, German, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Russian, Spanish and Turkish<ref>{{cite web|title=Microsoft Visual Studio 2015 Language Pack|url=https://www.microsoft.com/en-us/download/details.aspx?id=48157|website=microsoft.com|publisher=[[Microsoft]]|accessdate=29 August 2016}}</ref>
| genre                = [[Integrated development environment]]
| license              = [[Freemium]]<ref>{{Cite web |url=https://www.visualstudio.com/downloads/ |title=Visual Studio Downloads |work=visualstudio.com |publisher=[[Microsoft]] |accessdate=23 November 2013}}</ref>
| website              = {{url|https://www.visualstudio.com}}
}}

'''Microsoft Visual Studio''' is an [[integrated development environment]] (IDE) from [[Microsoft]]. It is used to develop [[computer program]]s for [[Microsoft Windows]], as well as [[web site]]s, [[web app]]s, [[web service]]s and [[mobile app]]s. Visual Studio uses Microsoft software development platforms such as [[Windows API]], [[Windows Forms]], [[Windows Presentation Foundation]], [[Windows Store]] and [[Microsoft Silverlight]]. It can produce both [[native code]] and [[managed code]].

Visual Studio includes a [[code editor]] supporting [[IntelliSense]] (the [[code completion]] component) as well as [[code refactoring]]. [[Microsoft Visual Studio Debugger|The integrated debugger]] works both as a source-level debugger and a machine-level debugger. Other built-in tools include a [[Profiling (computer programming)|code profiler]], forms designer for building [[GUI]] applications, [[web designer]], [[class (computing)|class]] designer, and [[database schema]] designer. It accepts plug-ins that enhance the functionality at almost every level—including adding support for [[source control]] systems (like [[Subversion (software)|Subversion]]) and adding new toolsets like editors and visual designers for [[domain-specific language]]s or toolsets for other aspects of the [[software development lifecycle]] (like the [[Team Foundation Server]] client: Team Explorer).

Visual Studio supports 36 different [[programming language]]s and allows the code editor and debugger to support (to varying degrees) nearly any programming language, provided a language-specific service exists. Built-in languages include [[C (programming language)|C]],<ref>{{cite web|last1=Brenner|first1=Pat|title=C99 library support in Visual Studio 2013|url=http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx|website=Visual C++ Team Blog|publisher=[[Microsoft]]|accessdate=3 August 2014|date=19 July 2013}}</ref> [[C++]] and [[C++/CLI]] (via [[Visual C++]]), [[VB.NET]] (via [[Visual Basic .NET]]), [[C Sharp (programming language)|C#]] (via [[Visual C Sharp|Visual C#]]), [[F Sharp (programming language)|F#]] (as of Visual Studio 2010<ref>http://research.microsoft.com/en-us/um/cambridge/projects/fsharp/</ref>) and [[TypeScript]] (as of Visual Studio 2013 Update 2). Support for other languages such as [[Python (programming language)|Python]],<ref>{{cite web|title=Best Python IDE For Python Programming|url=http://www.pythonicquest.com/article/best-python-ide/|website=Pythonic Quest|publisher=[[PythonicQuest]]|accessdate=17 January 2017|date=13 January 2017}}</ref> [[Ruby (programming language)|Ruby]], [[Node.js]], and [[MUMPS|M]] among others is available via language services installed separately. It also supports [[XML]]/[[XSLT]], [[HTML]]/[[XHTML]], [[JavaScript]] and [[Cascading Style Sheets|CSS]]. [[Java (programming language)|Java]] (and [[J Sharp|J#]]) were supported in the past.

Microsoft provides a free version of Visual Studio called the Community edition that supports plugins and is available at no cost.

==Architecture==
Visual Studio does not support any programming language, solution or tool intrinsically; instead, it allows the plugging of functionality coded as a VSPackage. When installed, the functionality is available as a ''Service''. The [[Integrated_development_environment|IDE]] provides three services: SVsSolution, which provides the ability to enumerate projects and solutions; SVsUIShell, which provides windowing and UI functionality (including tabs, toolbars and tool windows); and SVsShell, which deals with registration of VSPackages. In addition, the IDE is also responsible for coordinating and enabling communication between services.<ref name="vsenviron">{{cite web | url = https://msdn.microsoft.com/en-us/library/bb165114(VS.80).aspx | title = Visual Studio Development Environment Model | work=[[MSDN]] | publisher = [[Microsoft]] | accessdate = 1 January 2008}}</ref> All editors, designers, project types and other tools are implemented as VSPackages. Visual Studio uses [[Component Object Model|COM]] to access the VSPackages. The Visual Studio [[software development kit|SDK]] also includes the ''Managed Package Framework'' (''MPF''), which is a set of [[managed code|managed]] wrappers around the COM-interfaces that allow the Packages to be written in any [[List of CLI languages|CLI compliant language]].<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/bb166554(VS.80).aspx | title = VSPackages and Managed Package Framework (MPF) | publisher = [[Microsoft]] | work = [[MSDN]] | accessdate = 1 January 2008}}</ref> However, MPF does not provide all the functionality exposed by the Visual Studio COM interfaces.<ref name="extpage1"/>
The services can then be consumed for creation of other packages, which add functionality to the Visual Studio IDE.

Support for programming languages is added by using a specific VSPackage called a ''Language Service''. A language service defines various interfaces which the VSPackage implementation can implement to add support for various functionalities.<ref name = "langserv">{{cite web | url = https://msdn.microsoft.com/en-us/library/bb166391(VS.80).aspx | title = Language Service Essentials | accessdate = 1 January 2008 | publisher = [[Microsoft]] | work = [[MSDN]]}}</ref> Functionalities that can be added this way include syntax coloring, statement completion, brace matching, parameter information tooltips, member lists and error markers for background compilation.<ref name="langserv"/> If the interface is implemented, the functionality will be available for the language. Language services are implemented on a per-language basis. The implementations can reuse code from the parser or the compiler for the language.<ref name="langserv"/> Language services can be implemented either in [[native code]] or [[managed code]]. For native code, either the native COM interfaces or the Babel Framework (part of Visual Studio SDK) can be used.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/bb165670(VS.80).aspx | title = Babel Package Overview | publisher = [[Microsoft]] | work = [[MSDN]] | accessdate = 1 January 2008}}
</ref> For managed code, the MPF includes wrappers for writing managed language services.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/bb166360(VS.80).aspx | title = Managed Language Services overview | publisher = [[Microsoft]] | work = [[MSDN]] | accessdate = 1 January 2008}}</ref>

Visual Studio does not include any [[source control]] support built in but it defines two alternative ways for source control systems to integrate with the IDE.<ref name="scci">{{cite web | url = https://msdn.microsoft.com/en-us/library/bb165370.aspx | title = Source Control Integration Essentials | publisher = [[MSDN]] | accessdate = 19 September 2010}}</ref> A Source Control VSPackage can provide its own customised user interface. In contrast, a source control plugin using the ''MSSCCI'' (Microsoft Source Code Control Interface) provides a set of functions that are used to implement various source control functionality, with a standard Visual Studio user interface.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/bb166170.aspx | title = Source Control Plug-ins | publisher = [[MSDN]] | accessdate = 19 September 2010}}</ref><ref name="alan">{{cite web | url = http://alinconstantin.dtdns.net/webdocs/scc/MSSCCI.htm | title = Microsoft Source Code Control Interface | first = Alin | last = Constantin | accessdate = 3 January 2008}}</ref> MSSCCI was first used to integrate [[Visual SourceSafe]] with Visual Studio 6.0 but was later opened up via the Visual Studio SDK. Visual Studio .NET 2002 used MSSCCI 1.1, and Visual Studio .NET 2003 used MSSCCI 1.2. Visual Studio 2005, 2008 and 2010 use MSSCCI Version 1.3, which adds support for rename and delete propagation as well as asynchronous opening.<ref name="alan"/>

Visual Studio supports running multiple instances of the environment (each with its own set of VSPackages). The instances use different [[Windows Registry|registry hives]] (see [[MSDN]]'s [https://msdn.microsoft.com/en-us/library/ms724877(VS.85).aspx definition] of the term "registry '''hive'''" in the sense used here) to store their configuration state and are differentiated by their AppId (Application ID). The instances are launched by an AppId-specific .exe that selects the AppId, sets the root hive and launches the IDE. VSPackages registered for one AppId are integrated with other VSPackages for that AppId. The various product editions of Visual Studio are created using the different AppIds. The [[Visual Studio Express]] edition products are installed with their own AppIds, but the Standard, Professional and [[Visual Studio Team System|Team Suite]] products share the same AppId. Consequently, one can install the Express editions side-by-side with other editions, unlike the other editions which update the same installation. The professional edition includes a superset of the VSPackages in the standard edition and the team suite includes a superset of the VSPackages in both other editions. The AppId system is leveraged by the [[#Extensibility|Visual Studio Shell]] in Visual Studio 2008.<ref name="codefocus">{{cite web | url = http://www.code-magazine.com/focus/vsx/ | title = Visual Studio Extensibility | publisher = CoDe Magazine | accessdate = 1 January 2008}}</ref>

==Features==
===Code editor===
Like any other [[Integrated Development Environment|IDE]], it includes a [[code editor]] that supports [[syntax highlighting]] and [[autocomplete|code completion]] using [[IntelliSense]] for [[variable (programming)|variables]], [[subroutine|functions]], [[method (computer science)|methods]], [[Program loops|loops]] and [[LINQ]] queries.<ref name="vs2008editor"/> IntelliSense is supported for the included languages, as well as for [[XML]] and for [[Cascading Style Sheets]] and [[JavaScript]] when developing web sites and [[web application]]s.<ref name="vs2008js">{{cite web | url = http://weblogs.asp.net/scottgu/archive/2007/06/21/vs-2008-javascript-intellisense.aspx | title = VS 2008 JavaScript IntelliSense | authorlink = Scott Guthrie | first = Scott | last = Guthrie | accessdate = 31 December 2007}}</ref><ref name="vs2008css">{{cite web | url = http://weblogs.asp.net/scottgu/archive/2007/07/25/vs-2008-web-designer-and-css-support.aspx | title = VS 2008 Web Designer and CSS Support | authorlink = Scott Guthrie | first = Scott | last = Guthrie | accessdate = 31 December 2007}}</ref> Autocomplete suggestions appear in a [[modeless]] [[list box]] over the code editor window, in proximity of the editing [[Cursor (computing)|cursor]]. In Visual Studio 2008 onwards, it can be made temporarily semi-transparent to see the code obstructed by it.<ref name="vs2008editor">{{cite web | url = http://weblogs.asp.net/scottgu/archive/2007/07/28/nice-vs-2008-code-editing-improvements.aspx | title = Nice VS 2008 Code Editing Improvements | authorlink = Scott Guthrie | first = Scott | last = Guthrie | accessdate = 31 December 2007}}</ref> The code editor is used for all supported languages.

The Visual Studio code editor also supports setting bookmarks in code for quick navigation. Other navigational aids include [[code folding|collapsing code blocks]] and [[incremental search]], in addition to normal text search and [[regular expression|regex]] search.<ref name="feat">
{{cite web | url = http://msdn.microsoft.com/msdntv/transcripts/20030327VSNETABTranscript.aspx | title = Visual Studio .NET - Top 10 Code Editor Tips and Tricks | publisher = [[MSDN]] TV | accessdate = 31 December 2007}}</ref> The code editor also includes a multi-item [[clipboard]] and a task list.<ref name="feat"/> The code editor supports code snippets, which are saved templates for repetitive code and can be inserted into code and customized for the project being worked on. A management tool for code snippets is built in as well. These tools are surfaced as floating windows which can be set to automatically hide when unused or docked to the side of the screen. The Visual Studio code editor also supports [[code refactoring]] including parameter reordering, variable and method renaming, [[interface (computing)|interface]] extraction and encapsulation of class members inside properties, among others.

Visual Studio features background compilation (also called incremental compilation).<ref name="bgcompile">{{cite web | url = http://www.panopticoncentral.net/archive/2004/02/25/276.aspx | title = Background compilation, part 1 | accessdate = 31 December 2007}}</ref><ref name="advbasics">{{cite web | url = http://msdn.microsoft.com/msdnmag/issues/05/06/AdvancedBasics/ | title = Scaling Up: The Very Busy Background Compiler | first = Matthew | last = Gertz | work = [[MSDN]] Magazine | publisher = [[Microsoft]] | accessdate = 31 December 2007}}</ref> As code is being written, Visual Studio compiles it in the background in order to provide feedback about syntax and compilation errors, which are flagged with a red wavy underline. Warnings are marked with a green underline. Background compilation does not generate executable code, since it requires a different compiler than the one used to generate executable code.<ref>{{cite web | url = http://www.tfabraham.com/blog/2005/12/background-compilation-in-visual-studio-2002-2003-and-2005/ | title = Background Compilation in Visual Studio 2002, 2003 and 2005 | first = Thomas F. | last = Abraham | accessdate = 10 November 2015}}</ref> Background compilation was initially introduced with [[Microsoft Visual Basic]] but has now been expanded for all included languages.<ref name="advbasics"/>

===Debugger===
{{Main article|Microsoft Visual Studio Debugger}}
Visual Studio includes a [[debugger]] that works both as a source-level debugger and as a machine-level debugger. It works with both [[managed code]] as well as [[native code]] and can be used for debugging applications written in any language supported by Visual Studio. In addition, it can also attach to running processes and monitor and debug those processes.<ref>{{cite web | title = Attaching to Running Processes | url = https://msdn.microsoft.com/en-us/library/3s68z0b3(VS.80).aspx | publisher = [[MSDN]] | accessdate = 31 December 2007}}</ref> If source code for the running process is available, it displays the code as it is being run. If source code is not available, it can show the [[disassembly]]. The Visual Studio debugger can also create [[memory dump]]s as well as load them later for debugging.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/d5zhxt22(VS.80).aspx | title = Dumps | publisher = [[MSDN]] | accessdate = 31 December 2007}}</ref> Multi-threaded programs are also supported. The debugger can be configured to be launched when an application running outside the Visual Studio environment crashes.

The debugger allows setting [[breakpoint]]s (which allow execution to be stopped temporarily at a certain position) and watches (which monitor the values of variables as the execution progresses).<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/5557y8b4(VS.80).aspx | title = Breakpoint Overview| publisher = [[MSDN]] | accessdate = 31 December 2007}}</ref> Breakpoints can be conditional, meaning they get triggered when the condition is met. Code can be [[program animation|stepped over]], i.e., run one line (of source code) at a time.<ref name="step">{{cite web | url = https://msdn.microsoft.com/en-us/library/ek13f001(VS.80).aspx | title = Code Stepping Overview| publisher = [[MSDN]] | accessdate = 31 December 2007}}</ref> It can either ''step into'' functions to debug inside it, or ''step over'' it, i.e., the execution of the function body isn't available for manual inspection.<ref name="step"/> The debugger supports ''Edit and Continue'', i.e., it allows code to be edited as it is being debugged. When debugging, if the mouse pointer hovers over any variable, its current value is displayed in a tooltip ("data tooltips"), where it can also be modified if desired. During coding, the Visual Studio debugger lets certain functions be invoked manually from the <code>Immediate</code> tool window. The parameters to the method are supplied at the Immediate window.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/83hd8f1e(VS.80).aspx | title = Debugging at Design Time| publisher = [[MSDN]] | accessdate = 31 December 2007}}</ref>

===Designer===
Visual Studio includes a host of visual designers to aid in the development of applications. These tools include:

;Windows Forms Designer: The Windows Forms designer is used to build [[GUI]] applications using [[WinForms|Windows Forms]]. Layout can be controlled by housing the controls inside other containers or locking them to the side of the form. Controls that display data (like textbox, list box and grid view) can be [[data binding|bound]] to data sources like [[database]]s or [[LINQ|queries]]. Data-bound controls can be created by dragging items from the Data Sources window onto a design surface.<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/ms171923.aspx |title=Binding Controls to Data in Visual Studio |publisher=Msdn.microsoft.com |date= |accessdate=15 June 2013}}</ref> The UI is linked with code using an [[event-driven programming]] model. The designer generates either [[C Sharp (programming language)|C#]] or [[VB.NET]] code for the application.
;WPF Designer: The WPF designer, codenamed ''Cider'',<ref>{{cite web | url = http://www.microsoft.com/downloads/details.aspx?FamilyId=950D1EEC-5D4F-4A15-8250-D26E24B80A5D | title = MSDN TV: Introducing "Cider" - The Visual Studio Designer for WPF ("Avalon") | publisher = [[MSDN]] TV | accessdate = 1 January 2008}}</ref> was introduced with Visual Studio 2008. Like the Windows Forms designer it supports the drag and drop metaphor. It is used to author [[user interface]]s targeting [[Windows Presentation Foundation]]. It supports all WPF functionality including [[data binding]] and [[automatic layout]] management. It generates [[XAML]] code for the UI. The generated [[XAML]] file is compatible with [[Microsoft Expression Design]], the designer-oriented product. The XAML code is linked with code using a [[code-behind]] model.
;Web designer/development: Visual Studio also includes a web-site editor and designer that allows web pages to be authored by dragging and dropping widgets. It is used for developing [[ASP.NET]] applications and supports [[HTML]], [[CSS]] and [[JavaScript]]. It uses a [[code-behind]] model to link with ASP.NET code. From Visual Studio 2008 onwards, the layout engine used by the web designer is shared with [[Microsoft Expression Web]]. There is also [[ASP.NET MVC]] support for [[Model–view–controller|MVC]] technology as a separate download<ref>{{cite web|url=http://www.asp.net/mvc/ |title=MVC : The Official Microsoft ASP.NET Site |publisher=Asp.net |date=10 May 2013 |accessdate=15 June 2013}}</ref> and [[ASP.NET Dynamic Data]] project available from Microsoft.<ref>{{cite web|url=http://www.asp.net/DynamicData/ |title=Dynamic Data Content Map |publisher=Asp.net |date= |accessdate=15 June 2013}}</ref>
;Class designer: The Class Designer is used to author and edit the classes (including its members and their access) using [[Unified Modeling Language|UML]] modeling. The Class Designer can generate [[C Sharp (programming language)|C#]] and [[VB.NET]] code outlines for the classes and methods. It can also generate class diagrams from hand-written classes.
;Data designer: The data designer can be used to graphically edit [[database schema]]s, including typed tables, primary and foreign keys and constraints. It can also be used to design queries from the graphical view.
;Mapping designer: From Visual Studio 2008 onwards, the mapping designer is used by [[Language Integrated Query|LINQ to SQL]] to design the [[Object-Relational mapping|mapping]] between [[database schema]]s and the [[class (computing)|classes]] that encapsulate the data. The new solution from ORM approach, [[ADO.NET Entity Framework]], replaces and improves the old technology.

===Other tools===
;Open Tabs Browser: The open tabs browser is used to list all open tabs and to switch between them. It is invoked using <code>CTRL+TAB</code>.
;Properties Editor: The ''Properties Editor'' tool is used to edit properties in a GUI pane inside Visual Studio. It lists all available properties (both read-only and those which can be set) for all objects including [[class (computing)|classes]], forms, web pages and other items.
;Object Browser: The ''Object Browser'' is a [[namespace]] and [[class library]] browser for [[Microsoft .NET]]. It can be used to browse the namespaces (which are arranged hierarchically) in [[managed code|managed]] [[Assembly (CLI)|assemblies]]. The hierarchy may or may not reflect the organization in the file system.
;Solution Explorer: In Visual Studio parlance, a solution is a set of code files and other resources that are used to build an application. The files in a solution are arranged hierarchically, which might or might not reflect the organization in the file system. The ''Solution Explorer'' is used to manage and browse the files in a solution.
;Team Explorer: ''Team Explorer'' is used to integrate the capabilities of [[Team Foundation Server]], the [[Revision Control System]] into the IDE (and the basis for Microsoft's [[CodePlex]] hosting environment for open source projects). In addition to source control it provides the ability to view and manage individual work items (including bugs, tasks and other documents) and to browse [[Team Foundation Server|TFS]] statistics. It is included as part of a TFS install and is also available as a download for Visual Studio separately.<ref>{{cite web | url = http://download.microsoft.com/download/2/a/d/2ad44873-8ccb-4a1b-9c0d-23224b3ba34c/VSTFClient.img | title = Team Explorer 2005 (.img file)| publisher = [[Microsoft]] | accessdate = 5 March 2007}}</ref><ref>{{cite web | url = http://www.microsoft.com/downloads/details.aspx?familyid=0ed12659-3d41-4420-bbb0-a46e51bfca86&displaylang=en | title = Visual Studio Team System 2008 Team Explorer | publisher = [[Microsoft]] | accessdate = 5 March 2007}}
</ref> Team Explorer is also available as a stand-alone environment solely to access TFS services.
;Data Explorer: ''Data Explorer'' is used to manage databases on [[Microsoft SQL Server]] instances. It allows creation and alteration of database tables (either by issuing [[T-SQL]] commands or by using the Data designer). It can also be used to create [[database query|queries]] and [[stored procedure]]s, with the latter in either [[T-SQL]] or in [[managed code]] via [[SQL CLR]]. Debugging and [[IntelliSense]] support is available as well.
;Server Explorer: The ''Server Explorer'' tool is used to manage database connections on an accessible computer. It is also used to browse running [[Windows Service]]s, performance counters, [[Windows Event Log]] and [[message queue]]s and use them as a datasource.<ref>{{cite web | url = http://support.microsoft.com/kb/316649 | title = How to use the Server Explorer in Visual Studio .NET and Visual Studio 2005 | accessdate = 1 January 2008 | publisher = [[Microsoft]]}}</ref>
;PreEmptive Protection-Dotfuscator Community Edition: Visual Studio includes a free 'light' version of [[Dotfuscator]] by [[PreEmptive Solutions]] which obfuscates and hardens applications to help secure trade secrets (IP), reduce piracy/counterfeiting, protect against tampering and unauthorized debugging. Dotfuscator works with all flavors of .NET including ASP.NET, Xamarin, Unity and UWP.<ref>{{cite web|url=https://docs.microsoft.com/en-us/visualstudio/ide/dotfuscator/|title=Microsoft Visual Studio 2017 documentation: PreEmptive Protection - Dotfuscator .NET Obfuscator and Code Hardening Tool |publisher=Microsoft.com |date=15 March 2017 |accessdate=16 May 2017}}</ref>
;Text Generation Framework: Visual Studio includes a full text generation framework called [[Text Template Transformation Toolkit|T4]] which enables Visual Studio to generate text files from templates either in the IDE or via code.
;ASP.NET Web Site Administration Tool: The [[ASP.NET Web Site Administration Tool]] allows for the configuration of [[ASP.NET]] websites.
;Visual Studio Tools for Office: [[Visual Studio Tools for Office]] is a SDK and an add-in for Visual Studio that includes tools for developing for the [[Microsoft Office]] suite. Previously (for Visual Studio .NET 2003 and Visual Studio 2005) it was a separate SKU that supported only [[Visual C Sharp|Visual C#]] and [[Visual Basic .NET|Visual Basic]] languages or was included in the Team Suite. With Visual Studio 2008, it is no longer a separate SKU but is included with Professional and higher editions. A separate runtime is required when deploying VSTO solutions.

===Extensibility===
{{See also|List of Microsoft Visual Studio Add-ins|Visual Studio Extensibility}}
Visual Studio allows developers to write extensions for Visual Studio to extend its capabilities. These extensions "plug into" Visual Studio and extend its functionality. Extensions come in the form of ''macros'', [[List of Microsoft Visual Studio Add-ins|''add-ins'']], and ''packages''. Macros represent repeatable tasks and actions that developers can record programmatically for saving, replaying, and distributing. Macros, however, cannot implement new commands or create tool windows. They are written using [[Visual Basic]] and are not compiled.<ref name="extpage1">{{cite web | url = http://www.codeguru.com/csharp/.net/net_vs_addins/visualstudioadd-ins/article.php/c11835/ | title = Extending Visual Studio 2005 | first = Vijay | last = Mehta | work = CodeGuru | accessdate = 1 January 2008}}</ref> Add-Ins provide access to the Visual Studio object model and can interact with the IDE tools. Add-Ins can be used to implement new functionality and can add new tool windows. Add-Ins are plugged into the IDE via [[Component Object Model|COM]] and can be created in any COM-compliant languages.<ref name="extpage1"/> Packages are created using the Visual Studio [[Software Development Kit|SDK]] and provide the highest level of extensibility. They can create designers and other tools, as well as integrate other programming languages. The Visual Studio SDK provides unmanaged [[API]]s as well as a managed API to accomplish these tasks. However, the managed API isn't as comprehensive as the unmanaged one.<ref name="extpage1"/> Extensions are supported in the Standard (and higher) versions of Visual Studio 2005. [[Visual Studio Express|Express Editions]] do not support hosting extensions.

Visual Studio 2008 introduced the '''Visual Studio Shell''' that allows for development of a customized version of the IDE. The Visual Studio Shell defines a set of VSPackages that provide the functionality required in any IDE. On top of that, other packages can be added to customize the installation. The Isolated mode of the shell creates a new AppId where the packages are installed. These are to be started with a different executable. It is aimed for development of custom development environments, either for a specific language or a specific scenario. The Integrated mode installs the packages into the AppId of the Professional/Standard/Team System editions, so that the tools integrate into these editions.<ref name="codefocus"/> The Visual Studio Shell is available as a free download.

After the release of Visual Studio 2008, Microsoft created the Visual Studio Gallery. It serves as the central location for posting information about extensions to Visual Studio. Community developers as well as commercial developers can upload information about their extensions to Visual Studio .NET 2002 through Visual Studio 2010. Users of the site can rate and review the extensions to help assess the quality of extensions being posted. An extension is stored in a VSIX file.  Internally a VSIX file is a ZIP file that contains some XML files, and possibly one or more DLL's.  One of the main advantages of these extensions is that they do not require Administrator rights to be installed. RSS feeds to notify users on updates to the site and tagging features are also planned.<ref>{{cite web|last1=Cangialosi|first1=Anthony|title=The Visual Studio Gallery gets a little more community friendly|url=http://blogs.msdn.com/b/acangialosi/archive/2008/06/06/the-visual-studio-gallery-gets-a-little-more-community-friendly.aspx|website=Anthony @ MS|publisher=[[Microsoft]]|accessdate=3 August 2014|date=6 June 2008}}</ref>

==Supported products==
;[[Visual C++|Microsoft Visual C++]]: Microsoft Visual C++ is Microsoft's implementation of the [[C (programming language)|C]] and [[C++]] [[compiler]] and associated languages-services and specific tools for integration with the Visual Studio IDE. It can compile either in C mode or C++ mode. For C, it follows the [[C90 (C version)|1990 version of the ISO C]] standard with parts of [[C99]] specification along with MS-specific additions in the form of libraries.<ref>{{cite web | url = http://blogs.msdn.com/vcblog/archive/2007/11/05/iso-c-standard-update.aspx | title = ISO C Standard Update | website = Visual C++ Team Blog | publisher = [[Microsoft]] | accessdate = 2 January 2008}}</ref> For C++, it follows the [[ANSI C++]] specification along with a few [[C++11]] features.<ref>{{cite web | url = http://blogs.msdn.com/vcblog/archive/2007/06/04/update-on-the-c-0x-language-standard.aspx | title = Update On The C++-0x Language Standard | work = Visual C++ Team Blog | publisher = [[Microsoft]] }}</ref> It also supports the [[C++/CLI]] specification to write [[managed code]], as well as mixed-mode code (a mix of [[native code|native]] and [[managed code]]). Microsoft positions Visual C++ for development in native code or in code that contains both native as well as managed components. Visual C++ supports [[Component Object Model|COM]] as well as the [[Microsoft Foundation Classes|MFC]] library. For MFC development, it provides a set of wizards for creating and customizing MFC [[boilerplate code]], and creating GUI applications using MFC. Visual C++ can also use the Visual Studio forms designer to design UI graphically. Visual C++ can also be used with the [[Windows API]]. It also supports the use of ''intrinsic functions'',<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/26td21ds(VS.80).aspx | title = Compiler Intrinsics | publisher = [[MSDN]] | accessdate = 2 January 2008}}
</ref> which are functions recognized by the compiler itself and not implemented as a library. Intrinsic functions are used to expose the [[Streaming SIMD Extensions|SSE]] instruction set of modern CPUs. Visual C++ also includes the [[OpenMP]] (version 2.0) specification.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/tt15eb9t(VS.80).aspx | title = OpenMP in Visual C++ (Visual Studio 2005) |work=[[MSDN]] |publisher=Microsoft |accessdate=27 April 2013 |year=2005}}</ref>
;[[Visual C Sharp|Microsoft Visual C#]]: Microsoft Visual C#, Microsoft's implementation of the [[C Sharp (programming language)|C#]] language, targets the .NET Framework, along with the language services that lets the Visual Studio IDE support C# projects. While the language services are a part of Visual Studio, the compiler is available separately as a part of the .NET Framework. The Visual C# 2008, 2010 and 2012 compilers support versions 3.0, 4.0 and 5.0 of the C# language specifications, respectively. Visual C# supports the Visual Studio Class designer, Forms designer, and Data designer among others.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/kx37x362.aspx | title = Visual C# (MSDN) | publisher = [[MSDN]] | accessdate = 1 June 2009}}</ref>
;[[Visual Basic .NET|Microsoft Visual Basic]]: Microsoft Visual Basic is Microsoft's implementation of the [[VB.NET]] language and associated tools and language services. It was introduced with Visual Studio .NET (2002). Microsoft has positioned Visual Basic for [[Rapid Application Development]].<ref>{{cite web | url=https://msdn.microsoft.com/en-us/library/aa302334.aspx|date=October 2010|title=Make Your Components Really RAD with Visual Studio .NET Property Browser}}</ref><ref>{{cite web | url=https://msdn.microsoft.com/en-us/library/aa984213%28VS.71%29.aspx|date=October 2010|title=What's New in Visual Basic and Visual C#}}</ref> Visual Basic can be used to author both console applications as well as GUI applications. Like Visual C#, Visual Basic also supports the Visual Studio Class designer, Forms designer, and Data designer among others. Like C#, the VB.NET compiler is also available as a part of .NET Framework, but the language services that let VB.NET projects be developed with Visual Studio, are available as a part of the latter.
;Microsoft Visual Web Developer: Microsoft Visual Web Developer is used to create web sites, [[web application]]s and [[web service]]s using ASP.NET. Either [[C Sharp (programming language)|C#]] or [[VB.NET]] languages can be used. Visual Web Developer can use the Visual Studio Web Designer to graphically design web page layouts.
;[[Team Foundation Server]]: Team Foundation Server is intended for collaborative [[software development]] projects and acts as the server-side backend providing [[source control]], data collection, [[report]]ing, and project-tracking functionality. It also includes the ''Team Explorer'', the client tool for [[Team Foundation Server|TFS]] services, which is integrated inside Visual Studio Team System.

===Previous products===
;[[Visual FoxPro]]: Visual FoxPro is a data-centric [[object-oriented]] and [[procedural programming|procedural]] [[programming language]] produced by [[Microsoft]]. It derives from [[FoxPro 2|FoxPro]] (originally known as '''FoxBASE''') which was developed by Fox Software beginning in 1984. Visual FoxPro is tightly integrated with its own relational database engine, which extends FoxPro's xBase capabilities to support [[SQL]] queries and data manipulation. Visual FoxPro is a full-featured,<ref>{{cite web | url = http://msdn.microsoft.com/en-us/vfoxpro/bb190225.aspx | title = Visual FoxPro Home, under Visual FoxPro 9.0 Overview | publisher = [[MSDN]] | accessdate = 8 March 2014}}</ref> [[dynamic programming language]] that does not require the use of an additional general-purpose programming environment. In 2007, Visual FoxPro was discontinued after version 9 Service Pack 2. It was supported until 2015.<ref>{{cite web | url = http://msdn.microsoft.com/en-us/vfoxpro/bb308952.aspx | title = A Message to the Community | publisher = [[MSDN]] | accessdate = 2 January 2008}}</ref>

;[[Visual SourceSafe]]: Microsoft Visual SourceSafe is a [[source control]] [[software]] package oriented towards small software-development projects. The SourceSafe database is a multi-user, multi-process file-system database, using the Windows file system database primitives to provide locking and sharing support. All versions are multi-user, using [[Server Message Block|SMB]] (file server) networking.<ref>{{cite web|last=De |first=Alan |url=http://www.highprogrammer.com/alan/windev/sourcesafe.html |title=Visual SourceSafe: Microsoft's Source Destruction System |publisher=Highprogrammer.com |date= |accessdate=6 September 2009}}</ref><ref>{{cite web|url=http://support.microsoft.com/kb/q131022/ |title=INFO: Required Network Rights for the SourceSafe Directories |publisher=Support.microsoft.com |date=24 February 2005 |accessdate=6 September 2009}}</ref><ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/bb509342.aspx |title=Microsoft Visual SourceSafe Best Practices |publisher=Msdn.microsoft.com |date= |accessdate=6 September 2009}}
</ref> However, with Visual SourceSafe 2005, other [[client–server]] modes were added, Lan Booster and VSS Internet (which used [[HTTP]]/[[HTTPS]]). Visual SourceSafe 6.0 was available as a stand-alone product<ref>{{cite web|url=http://www.ecostsoftware.com/microsoft/microsoft-visual-sourcesafe-6_p2051 |title=Buy Microsoft Visual SourceSafe 6 (324-00269) :: eCostSoftware.com - UK Software Supplier |publisher=eCostSoftware.com |date= |accessdate=6 September 2009}}</ref> and was included with Visual Studio 6.0, and other products such as Office Developer Edition. Visual SourceSafe 2005 was available as a stand-alone product and included with the 2005 Team Suite. [[Team Foundation Server]] has superseded VSS as Microsoft's recommended platform for [[source control]].

;[[Visual J++|Microsoft Visual J++]]/[[Visual J Sharp|Microsoft Visual J#]]: Microsoft Visual J++ was [[Microsoft]]'s implementation of the [[Java (programming language)|Java]] language (with Microsoft-specific extensions) and associated language services. It was discontinued as a result of [[Sun Microsystems vs. Microsoft|litigation]] from [[Sun Microsystems]], and the technology was recycled into Visual J#, Microsoft's Java compiler for .NET Framework. J# was available with Visual Studio 2005 (supported until 2015) but was discontinued in Visual Studio 2008.

;[[Visual InterDev]]: Visual InterDev was used to create web applications using Microsoft [[Active Server Pages]] (ASP) technologies. It supports code completion and includes [[database]] server management tools. It has been replaced with Microsoft Visual Web Developer.

==Editions==
Microsoft Visual Studio is available in the following editions or [[Stock-keeping unit|SKUs]]:<ref name="Visual Studio Editions">{{cite web | url = https://www.visualstudio.com/vs/compare/ | title = Compare Visual Studio 2017 Offerings | publisher = Microsoft}}</ref>

===Community===
The Community edition was announced on 12 November 2014, as a new free version similar in functionality to Visual Studio Professional. Prior to this date, the only free editions of Visual Studio were the feature-limited Express variants. Unlike the Express variants, Visual Studio Community supports multiple languages, and provides support for extensions. Visual Studio Community is oriented towards individual developers and small teams.<ref name="vb-vscommunity">{{cite web|url=https://venturebeat.com/2014/11/12/microsoft-debuts-visual-studio-2015-and-net-2015-previews-free-visual-studio-community-2013/|title=Microsoft debuts Visual Studio 2015 and .NET 2015 previews, free Visual Studio Community 2013|website=VentureBeat|accessdate=12 November 2014}}</ref><ref name="vb-vscommunity2">{{cite web|url=https://techcrunch.com/2014/11/12/microsoft-makes-visual-studio-free-for-small-teams/|title=Microsoft Launches Free, Unrestricted Version Of Visual Studio For Small Teams|publisher=TechCrunch|accessdate=12 November 2014}}</ref>

===Professional===
As of Visual Studio 2010, the Professional edition is the entry level [[Commercial software|commercial edition]] of Visual Studio. (Previously, a more feature restricted Standard edition was available.)<ref name="VS 2010 Licensing Changes">{{cite web |url = http://blogs.msdn.com/b/bharry/archive/2009/10/19/vs-2010-licensing-changes.aspx | title = VS 2010 Licensing Changes | publisher = Microsoft | accessdate = 22 June 2010}}</ref> It provides an IDE for all supported development languages. [[MSDN]] support is available as MSDN Essentials or the full [[MSDN library]] depending on licensing. It supports [[XML]] and [[XSLT]] editing, and can create deployment packages that only use [[ClickOnce]] and [[Windows Installer|MSI]]. It includes tools like Server Explorer and integration with [[Microsoft SQL Server]] also. Windows Mobile development support was included in Visual Studio 2005 Standard, however, with Visual Studio 2008, it is only available in Professional and higher editions. Windows Phone 7 development support was added to all editions in Visual Studio 2010. Development for [[Windows Mobile]] is no longer supported in Visual Studio 2010; it is superseded by [[Windows Phone 7]].

===Enterprise===
In addition to the features provided by the Professional edition, the Enterprise edition provides a new set of software development, database development, collaboration, metrics, architecture, testing and reporting tools.

===Test Professional===
The Test Professional edition was introduced with Visual Studio 2010. Its focus is the dedicated tester role. It includes support for the management of test environments, the ability to start and report on tests and to connect to Team Foundation Server. It does not include support for development or authoring of tests.<ref name="Visual Studio Editions"/>

===Express===
{{Main article|Microsoft Visual Studio Express}}
Visual Studio Express is a stripped-down version of Visual Studio for students and hobbyists, first introduced with Visual Studio 2005 and discontinued with Visual Studio 2015. Originally, it consisted of several editions, each of which targeted a single programming language. Visual Studio Express 2005, 2008 and 2010 consisted of the following editions that could have been installed side-by-side:
* [[Visual Basic .NET|Visual Basic]] Express
* [[Visual C++]] Express
* [[Microsoft Visual C Sharp|Visual C#]] Express
* Visual [[J Sharp|J#]] Express (2005 only)
* Visual Web Developer Express
* Visual Studio Express for [[Windows Phone]] (2010 only)
Visual Studio 2012, 2013 and 2015 consist of editions geared towards different platforms instead:
* '''Express for Web''': focuses on developing [[web apps]]
* '''Express for Windows''': focuses on developing [[Universal Windows Platform apps]]
* '''Express for Desktop''': focuses on developing traditional apps for Windows, using [[Windows API]]
* '''Team Foundation Server Express''': provides source control and application lifecycle management
* '''Express for Windows Phone''' (2012 only): focuses on software development for [[Windows Phone 7|Windows Phone 7.5]] and [[Windows Phone 8|8.0]]
Versions prior to 2013 Update 2 do not include support for plug-ins. [[x86-64|x64]] compilers are not included in the Visual Studio Express edition IDEs, but are available as part of a Windows Software Development Kit that can be installed separately.<ref>{{cite web | url = https://msdn.microsoft.com/en-us/library/9yb4317s(v=VS.100).aspx | title = How to: Configure Visual C++ Projects to Target 64-Bit Platforms | publisher = Microsoft| accessdate = 19 August 2010}}</ref> After an initial announcement<ref>{{cite web | url = https://arstechnica.com/information-technology/2012/05/no-cost-desktop-software-development-is-dead-on-windows-8 | title = No-cost desktop software development is dead on Windows 8 | publisher = Ars Technica}}</ref> that the Express 2012 release would be restricted to creating [[Windows 8]] [[Metro-style apps]], Microsoft responded to negative developer feedback by reversing that decision and announcing that desktop application development would also be supported.<ref>{{cite web | url = http://www.zdnet.com/blog/microsoft/microsoft-adds-windows-8-desktop-support-to-visual-studio-2012-express/12892 | title = Microsoft adds Windows 8 Desktop support to Visual Studio 2012 Express | publisher = ZDNet}}</ref>

==History==
Prior to Visual Studio Version 4.0, there were Visual Basic 3, Visual C++, Visual FoxPro and Visual SourceSafe as separate products.

{| class="wikitable plainrowheaders" style="text-align:center"
|-
! scope="col" | Product name
! scope="col" | Codename
! scope="col" | Version<br />number
! scope="col" | Supported .NET<br />Framework versions
! scope="col" | Supported .NET<br />Core versions
! scope="col" | Release date
|-
! scope="row" | Visual Studio 97
| ''Boston''<ref name="WPWCEP" /> || 5.0 || {{N/A}} || {{N/A}}|| {{dts|1997|02}}
|-
! scope="row" | Visual Studio 6.0
| ''Aspen''<br/>{{Citation needed|date=July 2017}} || 6.0 || {{N/A}} || {{N/A}}|| {{dts|1998|06}}
|-
! scope="row" | Visual Studio .NET (2002)
| ''Rainier''<br/>{{Citation needed|date=July 2017}} || 7.0 || 1.0|| {{N/A}} || {{dts|2002|02|13}}
|-
! scope="row" | Visual Studio .NET 2003
| ''Everett''<br/>{{Citation needed|date=July 2017}} || 7.1 || 1.1 || {{N/A}}|| {{dts|2003|04|24}}
|-
! scope="row" | Visual Studio 2005
| ''Whidbey''<br/>{{Citation needed|date=July 2017}} || 8.0 || 2.0, 3.0|| {{N/A}}|| {{dts|2005|11|07}}
|-
! scope="row" | Visual Studio 2008
| ''Orcas''<ref name="cn-orcas"/> || 9.0 || 2.0, 3.0, 3.5 || {{N/A}}|| {{dts|2007|11|19}}
|-
! scope="row" | Visual Studio 2010
| ''Dev10'',<ref name="cn-dev10" /> ''Rosario''<ref name="cn-rosario" /> || 10.0 || 2.0 – 4.0 || {{N/A}}|| {{dts|2010|04|12}}
|-
! scope="row" | Visual Studio 2012
| ''Dev11''<br/>{{Citation needed|date=July 2017}} || 11.0 || 2.0 – 4.5.2 || {{N/A}}|| {{dts|2012|09|12}}
|-
! scope="row" | Visual Studio 2013
| ''Dev12''<br/>{{Citation needed|date=July 2017}} || 12.0 || 2.0 – 4.5.2 || {{N/A}}|| {{dts|2013|10|17}}
|-
! scope="row" | Visual Studio 2015
| ''Dev14''<br/>{{Citation needed|date=July 2017}} || 14.0 || 2.0 – 4.6 || 1.0|| {{dts|2015|07|20}}
|-
! scope="row" | Visual Studio 2017<ref>{{Cite web|url=https://msdn.microsoft.com/magazine/mt790181 |title=Visual Studio 2017 - A Quick Look at Productivity Enhancements in Visual Studio 2017 RC |date=14 November 2016 |access-date=14 November 2016 |deadurl=bot: unknown |archiveurl=https://web.archive.org/web/20161114095838/https://msdn.microsoft.com/magazine/mt790181 |archivedate=14 November 2016 |df= }}</ref>
| ''Dev15''<br/>{{Citation needed|date=July 2017}} || 15.0 ||3.5 – 4.7<ref>https://www.visualstudio.com/en-us/productinfo/vs2017-compatibility-vs</ref> || 1.0-1.1<ref>https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/</ref>, 2.0<ref>https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/</ref> || {{dts|2017|03|07}}
|}

=== {{anchor|Visual Studio 97}} 97===
Microsoft first released Visual Studio (codenamed ''Boston'',<ref name = "WPWCEP"/>{{Dead link|date=July 2017}} for the [[Boston|city of the same name]], thus beginning the VS codenames related to places)<ref name = "WPWCEP">{{cite web |url = http://windowsphonesecrets.com/2010/05/18/what-im-doing-in-redmond/ |title = website on windows CE programming |publisher = Paul Thurrott |accessdate = 19 May 2010}}</ref> in 1997, bundling many of its programming tools together for the first time. Visual Studio 97 came in two editions: Visual Studio Professional and Visual Studio Enterprise, the professional edition has three CDs, and the enterprise on four CDs. It included Visual J++ 1.1 for Java programming and introduced Visual InterDev for creating dynamically generated web sites using Active Server Pages.{{citation needed|date=March 2013}} There was a single companion CD that contained the [[Microsoft Developer Network|Microsoft Developer Network library]].

Visual Studio 97 was Microsoft's first attempt at using the same development environment for multiple languages. Visual J++, InterDev, and the [[Microsoft Developer Network|MSDN Library]] had all been using the same 'environment', called Developer Studio.<ref>[http://support.microsoft.com/kb/192912 update & help from Microsoft website]</ref>

Visual Studio was also sold as a bundle with the separate IDEs used for Visual C++, Visual Basic and Visual FoxPro.<ref name="codefocus"/>

==={{anchor|Visual Studio 6.0 (1998)}} 6.0 (1998)===
The next version, version 6.0 (codenamed ''Aspen'', after the [[Aspen, Colorado|ski resort]] in Colorado),{{citation needed|date=March 2011}} was released in June 1998 and is the last version to run on the [[Windows 9x]] platform.<ref>{{cite web |url = http://msdn.microsoft.com/en-us/vstudio/aa700918.aspx |title = System Requirements (Visual Studio 6.0) |publisher = Microsoft Co. |accessdate = 2 January 2008}}</ref> Each version of each language in part also settled to v6.0, including Visual J++ which was prior v1.1, and Visual InterDev at the 1st release. The v6 edition of Microsoft was the core environment for the next four releases to provide programmers with an integrated look-alike platform. This led Microsoft to transition the development on the platform independent [[.NET Framework]].

Visual Studio 6.0 was the last version to include Visual J++,<ref>{{cite web|title=Visual J++ Solution Center|url=http://support.microsoft.com/gp/vjj|work=Support|publisher=Microsoft|accessdate=25 May 2013}}</ref><ref>{{cite web|title=Visual J++ 6.0|url=https://msdn.microsoft.com/en-us/library/ms950413.aspx|work=[[MSDN]]|publisher=Microsoft|accessdate=25 May 2013}}</ref> which Microsoft removed as part of a settlement with [[Sun Microsystems]] that required Microsoft Internet Explorer not to provide<!--dubious? They could if they followed Sun's rules? But chose not to?--> support for the [[Java virtual machine]].

Visual Studio 6.0 came in two editions: Professional and Enterprise.<ref>{{cite web
  | title = Features by Edition
  | publisher = Microsoft
  | url = http://msdn.microsoft.com/vstudio/previous/vs6/features/default.aspx
|archiveurl=https://web.archive.org/web/20040215012731/http://msdn.microsoft.com/vstudio/previous/vs6/features/default.aspx |archivedate=15 February 2004}}</ref> The Enterprise edition contained extra features not found in Professional edition, including:

* Application Performance Explorer
* Automation Manager
* Microsoft Visual Modeler
* RemAuto Connection Manager{{citation needed|date=March 2011}}
* Visual Studio Analyzer
Visual Studio was also sold as a bundle with the separate IDEs used for Visual C++, Visual Basic and Visual FoxPro.<ref name="codefocus"/>

==={{anchor|Visual Studio .NET (2002)}} .NET (2002) ===
Microsoft released Visual Studio .NET (VS.NET), codenamed ''Rainier'' (for [[Washington (U.S. state)|Washington's]] [[Mount Rainier]]),{{Citation needed|date=July 2017}} in February 2002 (the [[Development stage#Beta|beta version]] was released via [[Microsoft Developer Network]] in 2001). The biggest change was the introduction of a [[managed code]] development environment using the .NET Framework. Programs developed using .NET are not compiled to [[machine language]] (like C++ is, for example) but instead to a format called [[Microsoft Intermediate Language]] (MSIL) or [[Common Intermediate Language]] (CIL). When a CIL application executes, it is [[Just-in-time compilation|compiled while being executed]] into the appropriate machine language for the platform it is being executed on, thereby making code portable across several platforms. Programs compiled into CIL can be executed only on platforms which have an implementation of [[Common Language Infrastructure]]. It is possible to run CIL programs in [[Linux]] or [[Mac OS X]] using non-Microsoft .NET implementations like [[Mono (software)|Mono]] and [[DotGNU]].

This was the first version of Visual Studio to require an [[Windows NT|NT]]-based Windows platform.<ref>{{cite web | url = http://msdn.microsoft.com/en-us/vstudio/aa700866.aspx | title = System Requirements (Visual Studio .NET)| publisher = [[MSDN]] | accessdate = 2 January 2008}}</ref> The installer enforces this requirement.

Visual Studio .NET 2002 shipped in four editions: Academic, Professional, Enterprise Developer, and Enterprise Architect. Microsoft introduced [[C Sharp (programming language)|C#]] (C-sharp), a new programming language, that targets .NET. It also introduced the successor to Visual J++ called Visual J#. Visual J# programs use Java's language-syntax. However, unlike Visual J++ programs, Visual J# programs can only target the .NET Framework, not the [[Java Virtual Machine]] that all other Java tools target.

Visual Basic changed drastically to fit the new framework, and the new version was called Visual Basic .NET. Microsoft also added extensions to C++, called [[Managed Extensions for C++]], so .NET programs could be created in C++.

Visual Studio .NET can produce applications targeting Windows (using the Windows Forms part of the .NET Framework), the Web (using ASP.NET and [[Web Services]]) and, with an add-in, portable devices (using the .NET Compact Framework).

The Visual Studio .NET environment was rewritten to partially use .NET. All languages are versions of Visual Studio, it has a cleaner interface and greater cohesiveness.{{Citation needed|date=May 2010}} It is also more customizable with tool windows that automatically hide when not in use. While Visual FoxPro 7 started out as part of Visual Studio .NET 2002, and early VS betas allowed debugging inside VFP-based DLLs, it was removed before release to follow its own development track.{{Citation needed|date=October 2010}}

The internal version number of Visual Studio .NET 2002 is version 7.0. Microsoft released Service Pack 1 for Visual Studio .NET 2002 in March 2005.<ref>{{cite web | url = http://www.microsoft.com/downloads/details.aspx?FamilyID=c41d8159-b42f-4d06-a797-e510494976ee&displaylang=en | title = Visual Studio .NET 2002 SP1 | publisher = [[Microsoft]] | accessdate = 2 January 2008}}</ref>

==={{anchor|Visual Studio .NET 2003}} .NET 2003===
In April 2003, Microsoft introduced a minor upgrade to Visual Studio .NET called Visual Studio .NET 2003, codenamed ''Everett'' (for the [[Everett, Washington|city of the same name]]).{{Citation needed|date=July 2017}} It includes an upgrade to the .NET Framework, version 1.1, and is the first release to support developing programs for mobile devices, using ASP.NET or the .NET Compact Framework. The Visual C++ compiler's standards-compliance improved, especially in the area of [[partial template specialization]]. Visual C++ Toolkit 2003 is a version of the same C++ compiler shipped with Visual Studio .NET 2003 without the IDE that Microsoft made freely available. {{as of | 2010}} it is no longer available and the Express Editions have superseded it. The internal version number of Visual Studio .NET 2003 is version 7.1 while the file format version is 8.0.<ref name="hacks"/>

Visual Studio .NET 2003 shipped in four editions: Academic, Professional, Enterprise Developer, and Enterprise Architect. The Visual Studio .NET 2003 Enterprise Architect edition includes an implementation of [[Microsoft Visio]] 2002's modeling technologies, including tools for creating [[Unified Modeling Language]]-based visual representations of an application's architecture, and an [[object-role modeling]] (ORM) and logical database-modeling solution. "Enterprise Templates" were also introduced, to help larger development teams standardize coding styles and enforce policies around component usage and property settings.

Service Pack 1 was released 13 September 2006.<ref>{{cite web | url = http://www.microsoft.com/downloads/details.aspx?familyid=69D2219F-CE82-46A5-8AEC-072BD4BB955E&displaylang=en | title = Microsoft Visual Studio .NET 2003 Service Pack 1 | publisher = [[Microsoft]] | accessdate = 2 January 2008}}</ref>

==={{anchor|Visual Studio 2005}} 2005===
Visual Studio 2005, codenamed ''Whidbey'' (a reference to [[Whidbey Island]] in [[Puget Sound]]),{{Citation needed|date=July 2017}} was released online in October 2005 and to retail stores a few weeks later. Microsoft removed the ".NET" moniker from Visual Studio 2005 (as well as every other product with .NET in its name), but it still primarily targets the .NET Framework, which was upgraded to version 2.0. It is the last version available for [[Windows 2000]] and also the last version to be able to target [[Windows 98]], [[Windows Me]] and [[Windows NT 4.0]] for C++ applications.<ref>[https://msdn.microsoft.com/en-us/library/6sehtctf(v=VS.90).aspx How to: Modify WINVER and _WIN32_WINNT]</ref><ref>[https://msdn.microsoft.com/en-us/library/bb531344(v=VS.90).aspx Breaking Changes]</ref>

Visual Studio 2005's internal version number is 8.0 while the file format version is 9.0.<ref name="hacks">{{cite web | url = http://www.ondotnet.com/pub/a/dotnet/excerpt/vshacks_chap1/index.html?page=4 | title = Hacking Visual Studio | accessdate = 1 January 2008}}</ref> Microsoft released Service Pack 1 for Visual Studio 2005 on 14 December 2006.<ref>
{{cite web | url = http://www.microsoft.com/downloads/details.aspx?FamilyID=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en | title = Visual Studio 2005 Service Pack 1 | publisher = [[Microsoft]] | accessdate = 1 January 2008}}</ref> An additional update for Service Pack 1 that offers Windows Vista compatibility was made available on 3 June 2007.<ref>{{cite web | url = http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee-4acc0aace5b6&displaylang=en |title = Visual Studio Service Pack 1 Update | accessdate = 1 January 2008}}</ref>

Visual Studio 2005 was upgraded to support all the new features introduced in .NET Framework 2.0, including generics and ASP.NET 2.0. The [[IntelliSense]] feature in Visual Studio was upgraded for generics and new project types were added to support ASP.NET web services. Visual Studio 2005 also includes a local web server, separate from [[Internet Information Services|IIS]], that can host ASP.NET applications during development and testing. It also supports all [[Microsoft SQL Server|SQL Server]] 2005 databases. Database designers were upgraded to support the [[ADO.NET|ADO.NET 2.0]], which is included with .NET Framework 2.0. C++ also got a similar upgrade with the addition of [[C++/CLI]] which is slated to replace the use of [[Managed Extensions for C++|Managed C++]].<ref>{{cite web
|url=https://msdn.microsoft.com/en-us/library/xey702bw(VS.80).aspx
|title=New Language Features in Visual C++
|work=Visual Studio 2005 Visual C++ Language Reference
|publisher=MSDN
|accessdate=28 December 2006
}}</ref> Other new features of Visual Studio 2005 include the "Deployment Designer" which allows application designs to be validated before deployments, an improved environment for web publishing when combined with ASP.NET 2.0 and load testing to see application performance under various sorts of user loads. Starting with the 2005 edition, Visual Studio also added extensive 64-bit support. While the host development environment itself is only available as a 32-bit application, Visual C++ 2005 supports compiling for [[x86-64]] (AMD64 and Intel 64) as well as [[IA-64]] ([[Itanium]]).<ref>{{cite web
|url=http://blogs.msdn.com/deeptanshuv/archive/2006/04/11/573795.aspx
|title=64-bit and Visual Studio 2005
|date=11 April 2006
|accessdate=28 December 2006
}}</ref> The [[Windows SDK|Platform SDK]] included 64-bit compilers and 64-bit versions of the libraries.

Microsoft also announced [[Visual Studio Tools for Applications]] as the successor to [[Visual Basic for Applications]] (VBA) and VSA (Visual Studio for Applications). VSTA 1.0 was released to manufacturing along with [[Office 2007]]. It is included with Office 2007 and is also part of the Visual Studio 2005 SDK. VSTA consists of a customized IDE, based on the Visual Studio 2005 IDE, and a runtime that can be embedded in applications to expose its features via the .NET object model. Office 2007 applications continue to integrate with VBA, except for InfoPath 2007 which integrates with VSTA. Version 2.0 of VSTA (based on Visual Studio 2008) was released in April 2008.<ref>[http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.office.developer.office.sdks&tid=965b9d31-6310-45cb-89d3-d9948a8a10c9&cat=&lang=&cr=&sloc=&p=1 VSTA vs VSTO in Software Development Kits]. ''In the latest MSDN Flash email I just received, it announces the release of Visual Studio Tools for Applications 2.0 (VSTA).''</ref> It is significantly different from the first version, including features such as dynamic programming and support for [[Windows Presentation Foundation|WPF]], [[Windows Communication Foundation|WCF]], [[Windows Workflow Foundation|WF]], [[Language Integrated Query|LINQ]], and .NET 3.5 Framework.

==={{anchor|Visual Studio 2008}} 2008===
Visual Studio 2008,<ref>{{cite web |title=Microsoft Details Dynamic IT Strategy at Tech-Ed 2007 |url=http://www.earthtimes.org/articles/show/news_press_release,115898.shtml |accessdate=4 June 2007}}</ref> and Visual Studio Team System 2008<ref>{{cite web |last=Beehler |first=Jeff |title=Visual Studio Team System 2008 ships! |work=Jeff Beehler's Blog |publisher=[[Microsoft Developer Network|MSDN]] Blogs |date=19 November 2007 |url=http://blogs.msdn.com/b/jeffbe/archive/2007/11/19/visual-studio-team-system-2008-ships.aspx |accessdate=25 June 2010}}</ref><ref>{{cite web |title=Microsoft Windows Visual Studio Team System 2008 |work=MSDN Search |publisher=MSDN Social |year=2010 |url= http://social.msdn.microsoft.com/Search/en-US?query=Microsoft%20Windows%20Visual%20Studio%20Team%20System%202008&resultsLang=en-GB&ac=8 |accessdate=25 June 2010}}</ref> codenamed ''Orcas'' (a reference to [[Orcas Island]], also an island in [[Puget Sound]], like Whidbey for the previous 2005 release), were released to MSDN subscribers on 19 November 2007 alongside .NET Framework 3.5. The source code for the Visual Studio 2008 IDE is available under a [[shared source]] license to some of [[Microsoft]]'s partners and [[Independent software vendor|ISVs]].<ref name="cn-orcas">{{cite web |title=Microsoft to Give Partners More Access to Orcas IDE Code |url=http://www.eweek.com/article2/0,1895,2212505,00.asp |accessdate=6 November 2007}}</ref> Microsoft released Service Pack 1 for Visual Studio 2008 on 11 August 2008.<ref>{{cite web |title=Download Details: Microsoft Visual Studio 2008 Service Pack 1 (exe) |url= http://www.microsoft.com/downloads/details.aspx?FamilyID=fbee1648-7106-44a7-9649-6d9f6d58056e&DisplayLang=en |accessdate=11 August 2008}}</ref> The internal version number of Visual Studio 2008 is version 9.0 while the file format version is 10.0. Visual Studio 2008 is the last version to support targeting [[Windows 2000]] for C++ applications.<ref>[https://msdn.microsoft.com/en-us/library/ws0swas0(VS.100).aspx Windows Platforms (CRT)]</ref>

Visual Studio 2008 is focused on development of [[Windows Vista]], 2007 Office system, and Web applications. For visual design, a new [[Windows Presentation Foundation]] visual designer and a new [[HTML]]/[[CSS]] editor influenced by [[Microsoft Expression Web]] are included. [[J Sharp|J#]] is not included. Visual Studio 2008 requires .NET 3.5 Framework and by default configures compiled assemblies to run on .NET Framework 3.5, but it also supports multi-targeting which lets the developers choose which version of the .NET Framework (out of 2.0, 3.0, 3.5, [[Silverlight|Silverlight CoreCLR]] or .NET Compact Framework) the assembly runs on. Visual Studio 2008 also includes new [[code analysis]] tools, including the new [[Code Metrics]] tool (only in Team Edition and Team Suite Edition).<ref>{{cite web | work = [[eWeek]] | accessdate = 6 October 2007 | title = Microsoft Pushes Secure, Quality Code | first = Darryl K. | last = Taft | url = http://www.eweek.com/article2/0,1759,2192515,00.asp?kc=EWRSS03119TX1K0000594 }}</ref> For [[Visual C++]], Visual Studio adds a new version of [[Microsoft Foundation Classes]] (MFC 9.0) that adds support for the visual styles and UI controls introduced with [[Windows Vista]].<ref>{{cite web | url = http://www.codeguru.com/cpp/controls/buttonctrl/advancedbuttons/article.php/c14407/ | title = Whats New in MFC 9.0 (Orcas) | work = CodeGuru | accessdate = 2 January 2008}}</ref> For native and managed code interoperability, Visual C++ introduces the STL/CLR, which is a port of the [[C++]] [[Standard Template Library]] (STL) containers and algorithms to [[managed code]]. STL/CLR defines STL-like containers, [[iterator]]s and algorithms that work on [[C++/CLI]] [[managed code|managed]] objects.<ref>{{cite web | url = http://blogs.msdn.com/nikolad/archive/2006/06/16/STLCLR-Intro.aspx | title = What Is STL/CLR? | first = Nikola | last = Dudla | work = Developing Windows Applications by Mykola Dudar | publisher = [[Microsoft]] | accessdate = 2 January 2008}}</ref><ref>{{cite web | url = http://blogs.msdn.com/vcblog/archive/2006/08/02/686894.aspx | title = Libraries Work In Orcas | work = Visual C++ Team Blog | publisher = [[Microsoft]] | accessdate = 2 January 2008}}
</ref>

Visual Studio 2008 features include an [[XAML]]-based designer (codenamed ''Cider''), [[Workflow Foundation|workflow designer]], [[Language Integrated Query|LINQ]] to [[SQL]] designer (for defining the type mappings and object encapsulation for SQL Server data), [[XSLT]] debugger, [[JavaScript]] [[Intellisense]] support, JavaScript Debugging support, support for [[User Account Control|UAC]] [[Manifest (CLI)|manifests]], a [[concurrent programming|concurrent]] build system, among others.<ref>{{cite web | url = http://blog.csharp-online.net/?p=108 | title = Download Visual Studio 03/07 CTP | accessdate = 14 June 2007}}</ref> It ships with an enhanced set of UI widgets, both for [[Windows Forms]] and [[Windows Presentation Foundation|WPF]]. It also includes a multithreaded build engine ([[MSBuild]]) to compile multiple source files (and build the executable file) in a project across multiple [[thread (computing)|threads]] simultaneously. It also includes support for compiling [[icon (computing)|icon]] [[Resource (Windows)|resources]] in [[Portable Network Graphics|PNG]] format, introduced in Windows Vista. An updated [[XML Schema (W3C)|XML Schema]] designer was released separately some time after the release of Visual Studio 2008.<ref>{{cite web |title=XSD Designer in Visual Studio |url= http://www.msdner.com/dev-archive/204/153-1021-2046403.shtm |accessdate=1 January 2008}}</ref>

[[Microsoft Visual Studio Debugger|Visual Studio Debugger]] includes features targeting easier debugging of multi-threaded applications. In debugging mode, in the ''Threads'' window, which lists all the threads, hovering over a thread displays the stack trace of that thread in tooltips.<ref>{{cite web |authorlink=S. Somasegar | first = S. | last = Somasegar |title=Debugging and Profiling Features in VS 2008 |publisher=[[Microsoft]] |url= http://blogs.msdn.com/somasegar/archive/2007/09/14/debugging-and-profiling-features-in-vs-2008.aspx |accessdate=24 July 2007}}</ref> The threads can directly be named and flagged for easier identification from that window itself.<ref name="johnrobbin">{{cite web |url= http://www.wintellect.com/cs/blogs/jrobbins/archive/2007/08/01/neat-new-multithreaded-debugging-features-in-vs-2008.aspx |title=Neat New Multithreaded Debugging Features in VS 2008 |first=John |last=Robbin |accessdate= 24 September 2007}}</ref> In addition, in the code window, along with indicating the location of the currently executing instruction in the current thread, the currently executing instructions in other threads are also pointed out.<ref name="johnrobbin"/><ref>{{cite web |first=Scott |last=Hanselman |title=Multi-threaded Debugging in Visual Studio 2008 |url= http://www.hanselman.com/blog/MultithreadedDebuggingInVisualStudio2008.aspx |accessdate=24 September 2007}}</ref> The [[Microsoft Visual Studio Debugger|Visual Studio debugger]] supports integrated debugging of the .NET 3.5 Framework [[Base Class Library]] (BCL) which can dynamically download the BCL source code and [[debug symbol]]s and allow stepping into the BCL source during debugging.<ref>{{cite web |authorlink = Scott Guthrie | first = Scott | last = Guthrie |title=Releasing the Source Code for the .NET Framework Libraries |url= http://weblogs.asp.net/scottgu/archive/2007/10/03/releasing-the-source-code-for-the-net-framework-libraries.aspx |accessdate=4 October 2007}}</ref> {{As of | 2010}} a limited subset of the BCL source is available, with more library support planned for later.

==={{anchor|Visual Studio 2010}} 2010===
On 12 April 2010, Microsoft released Visual Studio 2010, codenamed ''Dev10'',<ref name="cn-dev10">[http://blogs.msdn.com/b/volkerw/archive/2009/05/18/visual-studio-2010-aka-dev10-beta-available-for-download.aspx Visual Studio 2010 aka. Dev10 Beta available for download]</ref> and [[.NET Framework 4]].<ref>[http://www.eweek.com/c/a/Application-Development/Microsoft-Releases-Visual-Studio-2010-NET-Framework-4-529948/ Microsoft Releases Visual Studio 2010, .NET Framework 4]</ref><ref>[http://www.thinkdigit.com/General/Microsoft-launches-Visual-Studio-2010-and-NET_4417.html Microsoft launches Visual Studio 2010 and .NET Framework 4]</ref>

The Visual Studio 2010 [[Integrated development environment|IDE]] was redesigned which, according to [[Microsoft]], clears the UI organization and "reduces clutter and complexity."<ref name="firstlook"/> The new IDE better supports multiple document windows and floating tool windows,<ref name="firstlook"/> while offering better multi-monitor support. The IDE shell has been rewritten using the [[Windows Presentation Foundation]] (WPF), whereas the internals have been redesigned using [[Managed Extensibility Framework]] (MEF) that offers more extensibility points than previous versions of the IDE that enabled add-ins to modify the behavior of the IDE.<ref>{{cite web | url = http://msmvps.com/blogs/carlosq/archive/2008/10/26/visual-studio-2010-extensibility-moving-beyond-add-ins-and-packages.aspx | title = Visual Studio 2010 Extensibility moving beyond add-ins and packages | first=Carlos |last=Quintero | accessdate = 18 April 2009}}</ref>

The new [[multi-paradigm programming language|multi-paradigm]] [[ML (programming language)|ML]]-variant [[F Sharp programming language|F#]] forms part of Visual Studio 2010.<ref name="F#">{{cite web | url = http://blogs.msdn.com/dsyme/archive/2008/12/10/fsharp-to-ship-as-part-of-visual-studio-2010.aspx | title = F# to ship as part of Visual Studio 2010 | accessdate = 10 December 2008}}</ref>

Visual Studio 2010 comes with [[.NET Framework 4]] and supports developing applications targeting [[Windows 7]].<ref name="firstlook">{{cite web | url = http://www.microsoft.com/visualstudio/en-us/products/2010/default.mspx | title = Visual Studio 2010 Team System First Look | publisher = [[Microsoft]] | accessdate = 18 April 2009 }}</ref> It supports [[IBM DB2]] and [[Oracle Database|Oracle]] databases, in addition to [[Microsoft SQL Server]].<ref name="firstlook"/> It has integrated support for developing [[Microsoft Silverlight]] applications, including an interactive designer.<ref name="firstlook"/> Visual Studio 2010 offers several tools to make [[parallel programming]] simpler: in addition to the [[Parallel Extensions]] for the .NET Framework and the [[Visual C++#vc10|Parallel Patterns Library]] for [[native code]], Visual Studio 2010 includes tools for debugging parallel applications. The new tools allow the visualization of parallel [[Parallel Extensions#TPL|Tasks]] and their runtime [[Call stack|stacks]].<ref>{{cite web | url = http://www.danielmoth.com/Blog/2008/11/debugging-parallel-applications-with.html | title = Debugging Parallel applications with VS2010 | first=Daniel |last=Moth | accessdate = 18 April 2008}}</ref> Tools for profiling parallel applications can be used for visualization of thread wait-times and thread migrations across processor cores.<ref>{{cite web | url = http://msdn.microsoft.com/en-us/magazine/cc817396.aspx | title = More support for parallelism in the next version of Visual Studio | accessdate = 23 April 2009 | publisher = [[MSDN]]}}</ref> Intel and Microsoft have jointly pledged support for a new Concurrency Runtime in Visual Studio 2010<ref>{{cite web | url = http://www.sdtimes.com/INTEL_MICROSOFT_CONVERGE_ON_PARALLEL_COMPUTING/About_PARALLELPROGRAMMING_and_WINDOWS_and_INTEL_and_MICROSOFT/32731 | title = SD Times: Intel, Microsoft converge on parallel computing | first=David |last=Worthington | accessdate = 20 August 2008}}
</ref>
and Intel has launched parallelism support in [[Parallel Studio]] as an add-on for Visual Studio.<ref>{{cite web | url = http://sdtimes.com/link/33497 | title = Intel addresses development life cycle with Parallel Studio | first=David |last=Worthington | accessdate = 26 May 2009}}</ref>

The Visual Studio 2010 code editor now highlights references; whenever a symbol is selected, all other usages of the symbol are highlighted.<ref name="dev10soma">{{cite web | authorlink=S. Somasegar |first=S. |last=Somasegar | accessdate = 18 April 2008 | title = Code Focused Development in VS 2010 | url = http://blogs.msdn.com/somasegar/archive/2008/12/19/code-focused-development-in-vs-2010.aspx }}</ref> It also offers a ''Quick Search'' feature to [[Incremental find|incrementally search]] across all symbols in C++, C# and VB.NET projects. Quick Search supports substring matches and [[camelCase]] searches.<ref name="dev10soma"/> The ''Call Hierarchy'' feature allows the developer to see all the methods that are called from a current method as well as the methods that call the current one.<ref name="dev10soma"/> [[IntelliSense]] in Visual Studio supports a ''consume-first'' mode which developers can opt into. In this mode, IntelliSense does not auto-complete identifiers; this allows the developer to use undefined identifiers (like variable or method names) and define those later. Visual Studio 2010 can also help in this by automatically defining them, if it can infer their types from usage.<ref name="dev10soma"/> Current versions of Visual Studio have a known bug which makes IntelliSense unusable for projects using pure C (not C++).<ref>{{cite web | accessdate = 28 August 2011 | title = Bug: Intellisense believes itself in C++ while working on a C file. | url = http://social.msdn.microsoft.com/Forums/en/vcprerelease/thread/54995196-ab08-416d-9ddf-475bfb161779 }}</ref>

Visual Studio 2010 features a new [[Microsoft Help Viewer|Help System]] replacing the [[MSDN Library]] viewer. The Help System is no longer based on [[Microsoft Help 2]] and does not use Microsoft Document Explorer. Dynamic help containing links to related help topics based on where the developer was in the IDE has been removed in the shipping product,<ref>[http://leedumond.com/blog/dynamic-help-removed-from-visual-studio-2010/ Dynamic Help Removed From Visual Studio 2010]</ref> but can be added back using a download from Microsoft.<ref>{{cite web | accessdate = 13 July 2010 | title = Help Viewer Power Tool  | url = http://visualstudiogallery.msdn.microsoft.com/en-us/60a86afe-159b-4940-a22f-4fef055cbd63 }}</ref>

Visual Studio 2010 no longer supports development for Windows Mobile prior to [[Windows Phone 7]]. Visual Studio 2010 Service Pack 1 was released in March 2011.<ref>[http://www.microsoft.com/download/en/details.aspx?id=23691 Microsoft Visual Studio 2010 Service Pack 1 (Installer)]</ref>

====Ultimate 2010====
Visual Studio Ultimate 2010 replaces Visual Studio 2008 Team Suite.<ref>{{cite web | url = http://blogs.msdn.com/b/dannawi/archive/2010/01/07/visual-studio-2010-transition-benefits-the-ultimate-offer-what-you-need-to-know.aspx | title = Visual Studio 2010 transition benefits: "the ultimate offer" – What you need to know | publisher = [[Microsoft]] MSDN Blogs | accessdate = 14 September 2014}}</ref> It includes new modeling tools,<ref name="Gasp! Microsoft unveils its!">{{cite web|url=https://news.microsoft.com/2008/09/29/microsoft-unveils-next-version-of-visual-studio-and-net-framework/ |title=Microsoft Unveils Next Version of Visual Studio and .NET Framework |work=News Center |publisher=[[Microsoft]] |location=[[Redmond, Washington|Redmond]], Washington |accessdate=14 August 2009 |deadurl=no |archive-url=https://web.archive.org/web/20090815083038/http://www.microsoft.com/presspass/press/2008/sep08/09-29VS10PR.mspx |archive-date=15 August 2009 |df= }}</ref> such as the ''Architecture Explorer'',  which graphically displays projects and classes and the relationships between them.<ref name="cn-rosario">{{cite web | url = http://visualstudiomagazine.com/columns/article.aspx?editorialsid=2583 | title = Doing Architecture with Team System Rosario | accessdate = 18 April 2009}}</ref><ref name="aj">{{cite web | url = http://ajdotnet.wordpress.com/2009/03/29/visual-studio-2010-architecture-edition/ | title = Visual Studio 2010 Architecture Edition | accessdate = 18 April 2009}}
</ref>
It supports [[Unified Modeling Language|UML]] activity diagram, component diagram, (logical) class diagram, sequence diagram, and use case diagram.<ref name="aj"/> 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.<ref>{{cite web | url = http://channel9.msdn.com/posts/VisualStudio/Historical-Debugger-and-Test-Impact-Analysis-in-Visual-Studio-Team-System-2010/ | title = Historical Debugger and Test Impact Analysis in Visual Studio Team System 2010 | publisher = [[Channel 9 (Microsoft)|Channel 9]] | accessdate = 18 April 2009}}</ref> 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.<ref>{{cite web | title = What's new in Visual Studio Team System 2010: Episode 2 | url = http://blogs.msdn.com/habibh/archive/2008/10/01/what-s-new-in-visual-studio-team-system-2010-issue-2.aspx | first=Habib |last=Heydarian | accessdate = 18 April 2008}}</ref> 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 machine]]s are tagged with checkpoints which can later be investigated for issues, as well as to reproduce the issue.<ref>{{cite web | url = http://blogs.microsoft.co.il/blogs/maordavid/archive/2008/12/22/visual-studio-2010-lab-management.aspx | title = Visual Studio 2010 Lab Management | accessdate = 18 April 2009}}</ref> 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.<ref>{{cite web |title=Visual Studio 2010 to come with 'black box' |first=Ina |last=Fried |accessdate=18 April 2009 |url=http://news.cnet.com/8301-13860_3-10052412-56.html |publisher=[[CBS Interactive]] |work=[[CNET]]}}</ref>

==={{anchor|Visual Studio 2012}} 2012===
[[File:Visual Studio 2012 logo and wordmark.svg|thumb|right|Microsoft Visual Studio 2012 logo]]

Final build of Visual Studio 2012 was announced on 1 August 2012 and the official launch event was held on 12 September 2012.<ref>{{cite web|url=http://blogs.msdn.com/b/somasegar/archive/2012/08/01/visual-studio-2012-and-net-4-5-complete.aspx |title=Visual Studio 2012 and .NET 4.5 Complete! - Somasegar's blog - Site Home - MSDN Blogs |publisher=Blogs.msdn.com |date=1 August 2012 |accessdate=15 June 2013}}</ref>

Unlike prior versions, Visual Studio 2012 cannot record and play [[DTE80|macros]] and the macro editor has been removed.<ref>{{cite web|url=http://stackoverflow.com/questions/12062515/can-i-record-play-macros-in-visual-studio-2012-2013 |title=Can I record/play Macros in Visual Studio 2012/2013? |publisher=stackoverflow.com |date=31 December 2013 |accessdate=31 December 2013}}</ref>

New features include support for [[WinRT]] and [[C++/CX]] (Component Extensions) and [[C++ AMP]] ([[GPGPU]] programming) Semantic Colorization.<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/hh409293%28v=vs.110%29.aspx |title=What's New for Visual C++ in Visual Studio 2012 |publisher=Msdn.microsoft.com |date=15 August 2012 |accessdate=15 June 2013}}</ref>

On 16 September 2011, a complete 'Developer Preview' of Visual Studio 11 was published on Microsoft's website. Visual Studio 11 Developer Preview requires Windows 7, Windows Server 2008 R2, Windows 8, or later operating systems.<ref>{{cite web
  |url = http://www.microsoft.com/download/en/details.aspx?DisplayLang=en&id=27538
  |title = Visual Studio® 11 Developer Preview Download
  |work = Microsoft Download Center
  |publisher = Microsoft Corporation
  |date = 16 September 2011
  |accessdate = 14 October 2011
}}</ref> Versions of [[Microsoft Foundation Class Library]] (MFC) and C runtime (CRT) included with this release cannot produce software that is compatible with Windows XP or Windows Server 2003 except by using native multi-targeting and foregoing the newest libraries, compilers, and headers.<ref>{{cite web
  |url = https://connect.microsoft.com/VisualStudio/feedback/details/690617
  |title = Bug: apps created with CRT and MFC vNext (11) cannot be used on Windows XP SP3
  |work = Microsoft Connect
  |publisher = Microsoft Corporation
  |date = 24 September 2011
  |accessdate = 14 October 2011
  |quote = This behavior is by design in MFC and CRT for Visual Studio vNext. The minimum supported operating systems are Windows Server 2008 SP2 and Windows Vista.
}}</ref> However, on 15 June 2012, a blog post on the VC++ Team blog announced that based on customer feedback, Microsoft would re-introduce native support for Windows XP targets (though not for XP as a development platform) in a version of Visual C++ to be released later in the fall of 2012.<ref>{{cite web
  |url = http://blogs.msdn.com/b/vcblog/archive/2012/06/15/10320645.aspx
  |title = Targeting Windows XP with C++ in Visual Studio 2012
  |work = Visual C++ Team blog
  |publisher = Microsoft Corporation
  |date = 15 June 2012
  |accessdate = 26 June 2012
}}</ref> "Visual Studio 2012 Update 1" (Visual Studio 2012.1) was released in November 2012. This update added support for Windows XP targets and also added other new tools and features (e.g. improved diagnostics and testing support for Windows Store apps).<ref>{{cite web
  |url = http://blogs.msdn.com/b/somasegar/archive/2012/11/26/visual-studio-2012-update-1-now-available.aspx
  |title = Visual Studio 2012 Update 1 is now available!
  |work = Somasegar's blog
  |publisher = Microsoft Corporation
  |date = 26 November 2012
  |accessdate = 29 December 2012
}}</ref>

On 24 August 2011, a blog post by Sumit Kumar, a Program Manager on the Visual C++ team, listed some of the features of the upcoming version of the Visual Studio C++ IDE:<ref name="VC++ Team Blog Post">{{cite news
  |last = Kumar
  |first = Sumit
  |title=First Look at the New C++ IDE Productivity Features in the Next Version of Visual Studio
  |url=http://blogs.msdn.com/b/vcblog/archive/2011/08/24/10200097.aspx
  |work = VC++ Team Blog
  |agency = MSDN Blogs
  |publisher = Microsoft Corporation
  |date = 24 August 2011
  |accessdate = 14 October 2011
}}</ref>

* '''Semantic colorization''': Improved syntax coloring, various user-defined or default colors for C++ syntax such as macros, enumerations, typenames and functions.<ref name="VC++ Team Blog Post"/>
* '''Reference highlighting''': Selection of a symbol highlights all of the references to that symbol within scope.<ref name="VC++ Team Blog Post"/>
* '''New Solution Explorer''': The new Solution Explorer allows for visualization of class and file hierarchies within a solution/project. It can search for calls to functions and uses of classes.<ref name="VC++ Team Blog Post"/>
* '''Automatic display of IntelliSense list''': IntelliSense is automatically displayed whilst typing code, as opposed to previous versions where it had to be explicitly invoked through use of certain operators (i.e. the scope operator (::)) or shortcut keys (''Ctrl-Space'' or ''Ctrl-J'').<ref name="VC++ Team Blog Post"/>
* '''Member list filtering''': IntelliSense uses [[fuzzy logic]] to determine which functions/variables/types to display in the list.<ref name="VC++ Team Blog Post"/>
* '''Code snippets''': Code snippets are included in IntelliSense to automatically generate relevant code based on the user's parameters, custom code snippets can be created.<ref name="VC++ Team Blog Post"/>

The source code of Visual Studio 2012 consists of approximately 50 million lines of code.<ref>{{cite web|url=http://blogs.msdn.com/b/visualstudio/archive/2012/06/20/the-visual-studio-2012-feedback-tool-a-better-way-to-submit-bugs.aspx |title=The Visual Studio 2012 Feedback Tool: A better way to submit bugs - The Visual Studio Blog - Site Home - MSDN Blogs |publisher=Blogs.msdn.com |date=28 January 2013 |accessdate=15 June 2013}}</ref>

====Interface backlash====
During Visual Studio 11 beta, Microsoft eliminated the use of color within tools except in cases where color is used for notification or status change purposes. However, the use of color was returned after feedback demanding more contrast, differentiation, clarity and "energy" in the user interface.<ref>[http://visualstudiomagazine.com/articles/2012/05/08/color-returns-to-visual-studio-11-user-interface.aspx Color Returns to Visual Studio 11 User Interface]</ref><ref>[http://blogs.msdn.com/b/visualstudio/archive/2012/05/08/visual-studio-11-user-interface-updates-coming-in-rc.aspx Visual Studio 11 User Interface Updates Coming in RC]</ref>

In Visual Studio 2012 RC, a major change to the interface is the use of all-caps menu bar, as part of the campaign to keep Visual Studio consistent with the direction of other Microsoft user interfaces, and to provide added structure to the top menu bar area.<ref>[http://blogs.msdn.com/b/visualstudio/archive/2012/06/05/a-design-with-all-caps.aspx A DESIGN WITH ALL-CAPS]</ref> The redesign was criticized for being hard to read, and going against the trends started by developers to use [[CamelCase]] to make words stand out better.<ref>[http://www.i-programmer.info/news/177-windows-8/4324-microsoft-ignores-usability-and-users-vs-2012-keeps-all-cap-menus.html Microsoft Ignores Usability and Users - VS 2012 Keeps ALL-CAPS Menus]</ref> Some speculated that the root cause of the redesign was to incorporate the simplistic look and feel of Metro apps.<ref>[http://arktronic.com/weblog/2012-05-09/visual-studio-11s-redesign-awkwardness On Visual Studio 11's redesign awkwardness]</ref> However, there exists a [[Windows Registry]] option to allow users to disable the all-caps interface.<ref>[http://www.richard-banks.org/2012/06/how-to-prevent-visual-studio-2012-all.html How To Prevent Visual Studio 2012 ALL CAPS Menus!]</ref>

==={{anchor|Visual Studio 2013}} 2013===
The preview for Visual Studio 2013 was announced at the Build 2013 conference and made available on 26 June 2013.<ref>[http://blogs.msdn.com/b/visualstudio/archive/2013/06/26/visual-studio-2013-preview-available-now.aspx Visual Studio 2013 Preview Available Now!] Microsoft Visual Studio Blog, 26 June 2013</ref> The Visual Studio 2013 RC (Release Candidate) was made available to developers on MSDN on 9 September 2013.<ref>[http://blogs.msdn.com/b/visualstudio/archive/2013/09/09/visual-studio-2013-rc-available-now.aspx Visual Studio 2013 RC available now!] Microsoft Visual Studio Blog, 9 September 2013</ref>

The final release of Visual Studio 2013 became available for download on 17 October 2013 along with .NET 4.5.1.<ref>[http://blogs.msdn.com/b/visualstudio/archive/2013/10/17/visual-studio-2013-released-to-web.aspx Visual Studio 2013 released to web!] Microsoft Visual Studio Blog, 17 October 2013</ref> Visual Studio 2013 officially launched on 13 November 2013 at a virtual launch event keynoted by S. Somasegar and hosted on {{url|http://events.visualstudio.com}}.<ref>{{cite web |authorlink=S. Somasegar | first = S. | last = Somasegar |title=Visual Studio 2013 Launch: Announcing Visual Studio Online |publisher=MSDN Blogs |url=http://blogs.msdn.com/b/somasegar/archive/2013/11/13/visual-studio-2013-launch-announcing-visual-studio-online.aspx |accessdate=23 January 2014}}</ref> "Visual Studio 2013 Update 1" (Visual Studio 2013.1) was released on 20 January 2014.<ref>{{cite web
  |url = http://www.visualstudio.com/en-us/news/2014-jan-20-vs
  |title = Visual Studio 2013 Update 1
  |work = Visual Studio site
  |publisher = Microsoft Corporation
  |date = 20 January 2014
  |accessdate = 23 January 2014
}}</ref>
Visual Studio 2013.1 is a targeted update that addresses some key areas of customer feedback.<ref>{{cite web
  |url = http://blogs.msdn.com/b/somasegar/archive/2014/01/20/visual-studio-2013-update-1.aspx
  |title = Visual Studio 2013 Update 1
  |work = Somasegar's blog
  |publisher = Microsoft Corporation
  |date = 20 January 2014
  |accessdate = 23 January 2014
}}</ref>
"Visual Studio 2013 Update 2" (Visual Studio 2013.2) was released on 12 May 2014.<ref>{{cite web
  |url = http://www.visualstudio.com/en-us/news/2014-may-12-vs
  |title = Visual Studio 2013 Update 2 RTM
  |work = Visual Studio site
  |publisher = Microsoft Corporation
  |date = 12 May 2014
  |accessdate = 12 July 2014
}}</ref>
Visual Studio 2013 Update 3 was released on 4 August 2014. With this update, Visual Studio provides an option to disable the all-caps menus, which was introduced in VS2012.<ref>{{cite web
  |url = http://support.microsoft.com/kb/2933779
  |title=Description of Visual Studio 2013 Update 3
  |publisher = Microsoft Corporation
  |date = 15 August 2014
  |accessdate = 18 August 2014
}}</ref>
"Visual Studio 2013 Update 4" (Visual Studio 2013.4) was released on 12 November 2014.<ref>{{cite web
  |url = http://www.visualstudio.com/news/vs2013-update4-rtm-vs
  |title = Visual Studio 2013 Update 4 RTM
  |work = Visual Studio site
  |publisher = Microsoft Corporation
  |date = 12 November 2014
  |accessdate = 16 November 2014
}}</ref>
"Visual Studio 2013 Update 5" (Visual Studio 2013.5) was released on 20 July 2015.<ref>https://www.visualstudio.com/news/vs2013-update5-vs</ref>

==={{anchor|Visual Studio 2015}} 2015===
Initially referred to as Visual Studio "14", the first [[Community Technology Preview]] (CTP) was released on 3 June 2014<ref>{{cite web | url=http://blogs.msdn.com/b/visualstudio/archive/2014/06/03/visual-studio-14-ctp-now-available.aspx | title=Visual Studio "14" CTP now available | work=The Visual Studio Blog | date=3 June 2014 | accessdate=18 August 2014 | last=Montgomery | first=John}}</ref> and the [[Release Candidate]] was released on 29 April 2015; Visual Studio 2015 was officially announced as the final name on 12 November 2014.<ref>{{Cite web |url = http://blogs.msdn.com/b/visualstudio/archive/2014/11/12/visual-studio-2015-preview-visual-studio-community-2013-visual-studio-2013-update-4-and-more.aspx |title = Visual Studio 2015 Preview, Visual Studio Community 2013, Visual Studio 2013 Update 4, and More |date = 12 November 2014 |accessdate = 15 January 2015 |website = Visual Studio Blog |publisher=[[Microsoft]] |last = Montgomery |first = John}}</ref>

Visual Studio 2015 RTM was released on 20 July 2015.<ref>https://www.visualstudio.com/news/vs2015-vs</ref> Visual Studio 2015 Update 1 was released on 30 November 2015.<ref>https://www.visualstudio.com/news/vs2015-update1-vs</ref> Visual Studio 2015 Update 2 was released on 30 March 2016.<ref>https://www.visualstudio.com/en-us/news/vs2015-update2-vs.aspx</ref> Visual Studio 2015 Update 3 was released on 27 June 2016.<ref>https://www.visualstudio.com/en-us/news/releasenotes/vs2015-update3-vs</ref>

==={{anchor|Visual Studio 2017}} 2017===
[[File:Visual Studio 2017 logo and wordmark.svg|alt=Microsoft Visual Studio 2017 Logo|thumb|Microsoft Visual Studio 2017 logo]]
Initially referred to as Visual Studio "15", it was released on 7 March 2017.<ref>{{cite web |last1=Liuson| first1=Julia |title=Join Us: Visual Studio 2017 Launch Event and 20th Anniversary |url=https://blogs.msdn.microsoft.com/visualstudio/2017/02/09/visual-studio-2017-launch-event-and-20th-anniversary/ |website=The Visual Studio Blog |publisher=[[Microsoft]] |date=9 February 2017}}</ref> The first Preview was released on 30 March 2016.<ref>{{cite web |last1=Montgomery |first1=John |title=Visual Studio "15" Preview Now Available |url=https://blogs.msdn.microsoft.com/visualstudio/2016/03/30/visual-studio-15-preview/ |website=The Visual Studio Blog |publisher=[[Microsoft]] |date=30 March 2016}}</ref> Visual Studio "15" Preview 2 was released 10 May 2016.<ref>{{cite web |last1=Montgomery |first1=John |title=Visual Studio "15" Preview 2 |url=https://blogs.msdn.microsoft.com/visualstudio/2016/05/10/visual-studio-15-preview-2/ |website=The Visual Studio Blog |publisher=[[Microsoft]] |date=10 May 2016}}</ref><ref>{{Cite web |url=https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes |title=Visual Studio "15" Preview 2 |website=visualstudio.com |publisher=[[Microsoft]] |date=10 May 2016 |archive-url=https://web.archive.org/web/20160613114040/https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes |archive-date=13 June 2016 |deadurl=usurped}}</ref> Visual Studio "15" Preview 3 was released on 7 July 2016.<ref>{{cite web |last1=Montgomery |first1=John |title=Visual Studio "15" Preview 3 |url=https://blogs.msdn.microsoft.com/visualstudio/2016/07/07/visual-studio-15-preview-3/ |website=The Visual Studio Blog |publisher=[[Microsoft]] |date=7 July 2016}}</ref><ref>{{Cite web |url=https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes |title=Visual Studio "15" Preview 3 |website=visualstudio.com |publisher=[[Microsoft]] |date=7 July 2016 |archive-url=https://web.archive.org/web/20160715151136/https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes |archive-date=15 July 2016}}</ref>  Visual Studio "15" Preview 4 was released on 22 August 2016.<ref name ="mspoweruser">{{Cite web|url=http://mspoweruser.com/visual-studio-15-preview-4-now-available-for-download-with-new-installation-experience-and-more/|title=Visual Studio "15" Preview 4 Now Available For Download With New Installation Experience And More - MSPoweruser|date=22 August 2016|language=en-US|access-date=22 August 2016}}</ref><ref>{{Cite web|url=https://blogs.msdn.microsoft.com/visualstudio/2016/08/22/visual-studio-15-preview-4/|title=Visual Studio "15" Preview 4|website=blogs.msdn.microsoft.com|access-date=22 August 2016}}</ref> Visual Studio "15" Preview 5 was released on 5 October 2016.<ref>{{Cite web|url=https://blogs.msdn.microsoft.com/visualstudio/2016/10/05/announcing-visual-studio-15-preview-5/|title=Announcing Visual Studio "15" Preview 5|website=blogs.msdn.microsoft.com|access-date=5 October 2016}}</ref>

{{asof |2016 |04}}, Visual Studio is making the [[Ethereum]] [[Solidity]] language available to developers.<ref>{{cite web |last1=Davies |first1=Alex |title=Hyperledger blockchain code almost comes together for IoT |url=http://rethink-iot.com/2016/04/01/hyperledger-blockchain-code-almost-comes-together-for-iot/ |website=ReTHINK IoT |publisher=ReThink Research |date=1 April 2016}}</ref>

On 14 November 2016, for a brief period of time, Microsoft released a blog post revealing Visual Studio 2017 product name version alongside upcoming features.<ref>{{Cite web|url=https://msdn.microsoft.com/magazine/mt790181 |title=Visual Studio 2017 - A Quick Look at Productivity Enhancements in Visual Studio 2017 RC |date=14 November 2016 |access-date=14 November 2016 |deadurl=bot: unknown |archiveurl=https://web.archive.org/web/20161114095838/https://msdn.microsoft.com/magazine/mt790181 |archivedate=14 November 2016 |df= }}</ref>

On 16 November 2016, "Visual Studio 2017" was announced as the final name,<ref>{{Cite news|url=https://blogs.msdn.microsoft.com/visualstudio/2016/11/16/visual-studio-2017-rc/|title=Visual Studio 2017 Release Candidate|access-date=30 March 2017|language=en-US}}</ref> and Visual Studio 2017 [[Release candidate|RC]] was released.<ref name="rel2017">{{Cite web|url=https://blogs.msdn.microsoft.com/visualstudio/2017/03/07/announcing-visual-studio-2017-general-availability-and-more/|title=Announcing Visual Studio 2017 General Availability|last=|first=|date=|website=|access-date=}}</ref>

On 7 March 2017, Visual Studio 2017 was released for general availability.<ref name="rel2017" />

On 14 March 2017, first fix was released for Visual Studio 2017 due to failures during installation or opening solutions in the first release.<ref name="rel2017" />

On 5 April 2017, Visual Studio 2017 15.1 was released and added support for targeting the .NET Framework 4.7.

On 10 May 2017, Visual Studio 2017 15.2 was released and added a new workload, "Data Science and Analytical Applications Workload". An update to fix the dark color theme was released on 12 May 2017.

On 14 August 2017, Visual Studio 2017 15.3 was released and added support for targeting [[.NET Core]] 2.0. An update (15.3.1) was released four days later to address a [https://blogs.msdn.microsoft.com/devops/2017/08/15/git-vulnerability-with-submodules/ Git vulnerability with submodules] ([https://public-inbox.org/git/xmqqh8xf482j.fsf@gitster.mtv.corp.google.com/T/#u CVE 2017-1000117]).

Visual Studio 2017 offers new features like support for EditorConfig (a coding style enforcement framework), [[Native Image Generator|NGen]] support, [[.NET Core]] and [[Docker (software)|Docker]] toolset (Preview), and [[Xamarin]] 4.3 (Preview).<ref name="rel2017" /> It also has [[Extensible Application Markup Language|XAML]] Editor, improved IntelliSense, live unit testing, debugging enhancement and better IDE experience and productivity.<ref>{{Cite web|url=http://blog.ifourtechnolab.com/post/2016/12/22/visual-studio-2017-new-features-and-updates1|title=Visual Studio 2017 – New features and updates|last=|first=|date=|website=|publisher=iFour|access-date=26 December 2016}}</ref>

==Related products==
{{Missing information|[[Visual Studio Lab Management]], [[VSTS Profiler]]|date=November 2015}}

===Team Services===
{{Anchor|Visual Studio Online}}
On 13 November 2013, Microsoft announced the release of a [[software as a service]] offering of Visual Studio on [[Microsoft Azure]] platform; at the time, Microsoft called it Visual Studio Online. Previously announced as Team Foundation Services, it expands over [[Team Foundation Server]] by making it available on the Internet and implementing a [[rolling release]] model.<ref>{{cite web|last1=Blankenship|first1=Ed|title=Introducing Visual Studio Online|url=http://msdn.microsoft.com/en-us/magazine/dn519923.aspx|website=[[MSDN Magazine]]|publisher=[[Microsoft]]|date=January 2014}}</ref><ref>{{cite web|title=Features Timeline|url=http://www.visualstudio.com/en-us/news/release-archive-vso|website=VisualStudio.com|publisher=[[Microsoft]]}}</ref> Customers could use Azure portal to subscribe to Visual Studio Online. Subscribers receive a hosted [[Git (software)|Git]]-compatible [[version control system]], a load-testing service, a telemetry service and an in-browser code editor codenamed "Monaco".<ref>{{Cite web|url = http://www.infoworld.com/article/2609774/cloud-computing/microsoft-reinvents-visual-studio-as-an-azure-cloud-service.html|title = Microsoft reinvents Visual Studio as an Azure cloud service|date = 14 November 2013|accessdate = |website = [[InfoWorld]]|publisher = [[International Data Group|IDG]]|last = Yegulalp|first = Serdar}}</ref> During the ''{{not typo|Connect(); 2015}}'' developer event on 18 November 2015, Microsoft announced that the service name is changed to Visual Studio Team Services.<ref>{{cite web|last1=Harry|first1=Brian|title=News from Connect(); 2015|url=http://blogs.msdn.com/b/bharry/archive/2015/11/18/news-from-connect-2015.aspx|website=Brian Harry's blog|publisher=[[Microsoft]]|date=18 November 2015}}</ref>

Microsoft offers Basic, Professional, and Advanced subscription plans for Team Services. The Basic plan is free of charge for up to five users. Users with an MSDN subscription of Visual Studio can be added to a plan with no additional charge.<ref>{{cite web|title=Visual Studio Online Pricing Details|url=https://azure.microsoft.com/en-us/pricing/details/visual-studio-team-services/|website=Microsoft Azure|publisher=[[Microsoft]]|accessdate=29 November 2014}}</ref>

===Application Lifecycle Management===
Visual Studio Application Lifecycle Management (ALM) is a collection of integrated software development tools developed by Microsoft. These tools currently consist of the IDE (Visual Studio 2015 Community and greater editions), server (Team Foundation Server), and cloud services (Visual Studio Team Services).<ref>{{cite web|url=https://arstechnica.com/information-technology/2013/11/microsoft-takes-development-into-the-cloud-with-visual-studio-online/ |title=Microsoft takes development into the cloud with Visual Studio Online |work=[[Ars Technica]] |publisher=[[Condé Nast]] |first=Peter |last=Bright |date=12 November 2013 |accessdate=7 March 2016}}</ref> Visual Studio ALM supports team-based development and collaboration, Agile project management, [[DevOps]], source control, packaging, continuous development, automated testing, release management, continuous delivery, and reporting tools for apps and services.<ref>{{cite web|url=http://msdn.microsoft.com/library/fda2bad5.aspx |title=DevOps and Application Lifecycle Management |work=[[MSDN]] |publisher=[[Microsoft]] |date= |accessdate=3 March 2016}}</ref>

In Visual Studio 2005 and Visual Studio 2008, the brand was known as Microsoft Visual Studio Team System (VSTS). In October 2009, the Team System brand was renamed<ref name="Gasp! Microsoft unveils its!" /><ref>{{cite web | url = http://msdn.microsoft.com/en-us/vstudio/bb725993.aspx | title = Visual Studio Team System Rosario | accessdate = 5 April 2008}}</ref> Visual Studio ALM with the Visual Studio 2010 (codenamed 'Rosario') release.<ref>{{cite web
|url=http://blog.octavie.nl/index.php/2009/11/25/visual-studio-2010-team-system-session/
|title=Visual Studio 2010 Team System session
|first=Octavie |last=van Haaften
|work=SharePoint: Working on it…
|date=25 November 2009
|accessdate=8 December 2011
}}</ref>

Visual Studio Team Services debuted as Visual Studio Online in 2013 and was renamed in 2015.<ref>{{cite web
|url=https://blogs.msdn.microsoft.com/bharry/2015/11/18/news-from-connect-2015/
|title=News from Connect(); 2015
|first=Brian | last=Harry
|work=Brian Harry's blog
|publisher=[[Microsoft]]
|date=18 November 2015
|accessdate=3 March 2016
}}</ref>

{{Use dmy dates|date=June 2017}}

===Visual Studio LightSwitch===
Microsoft Visual Studio LightSwitch is an extension and framework specifically tailored for creating line-of-business applications built on existing .NET technologies and Microsoft platforms. The applications produced are architecturally [[Multitier architecture|3-tier]]: the user interface runs on either [[Silverlight|Microsoft Silverlight]] or [[HTML5|HTML 5 client]],<ref>{{cite web|url=http://msdn.microsoft.com/en-us/vstudio/htmlclient.aspx |title=LightSwitch HTML Client |website=[[MSDN]] |publisher=[[Microsoft]] |date= |accessdate=15 June 2013}}</ref> or as a SharePoint 2013 app;<ref>{{Cite web |url=http://blogs.msdn.com/b/bethmassi/archive/2013/01/17/get-started-building-sharepoint-apps-in-minutes-with-lightswitch.aspx |title=Get Started Building SharePoint Apps in Minutes with LightSwitch |last=Massi |first=Beth |date=17 January 2013 |website=Beth Massi's blog |publisher=[[Microsoft]]}}</ref> the logic and data-access tier is built on [[WCF Data Services]] and exposed as an [[OData]] feed hosted<ref>{{Cite web |url=http://blogs.msdn.com/b/lightswitch/archive/2012/03/22/lightswitch-architecture-odata.aspx |title=LightSwitch Architecture: OData (John Rivard) |last=Rivard |first=John |date=22 March 2012 |website=Visual Studio LightSwitch Team Blog |publisher=[[Microsoft]]}}</ref> in ASP.NET; and the primary data storage supports [[SQL Server Express|Microsoft SQL Server Express]], [[Microsoft SQL Server]] and [[SQL Azure|Microsoft SQL Azure]]. LightSwitch also supports other data sources including [[SharePoint|Microsoft SharePoint]], OData and WCF RIA Services.

LightSwitch includes graphical designers for designing entities and entity relationships, entity queries, and UI screens. Business logic may be written in either [[Visual Basic .NET|Visual Basic]] or [[Visual C Sharp|Visual C#]]. LightSwitch is included with Visual Studio 2012 Professional and higher. Visual Studio 2015 is the last release of Visual Studio that includes the LightSwitch tooling.<ref>{{cite web|url=https://blogs.msdn.microsoft.com/lightswitch/2016/10/14/lightswitch-update/ |title=LightSwitch Update |website=Visual Studio LightSwitch Team Blog |publisher=[[Microsoft]] |date=14 October 2016 }}</ref>

The user interface layer is now an optional component when deploying a LightSwitch solution, allowing a service-only deployment.<ref>{{Cite web |url=https://msdn.microsoft.com/en-us/library/vstudio/hh973447.aspx |title=How to: Deploy a LightSwitch OData Service |website=[[MSDN]] |publisher=[[Microsoft]] |access-date=15 June 2013}}</ref>

The first version of Visual Studio LightSwitch, released 26 July 2011,<ref>{{cite web|url=http://blogs.msdn.com/b/lightswitch/archive/2011/07/05/visual-studio-lightswitch-2011-is-launching-july-26th.aspx |title=Visual Studio LightSwitch 2011 is Launching July 26th! |work=Visual Studio LightSwitch Team Blog |publisher=[[Microsoft]] |date=5 July 2011}}</ref> had many differences from the current{{when|date=November 2014}} release of LightSwitch. Notably the tool was purchased and installed as a stand-alone product. If Visual Studio 2010 Professional or higher was already installed on the machine, LightSwitch would integrate into that.<ref>{{cite web |last=Massi |first=Beth | url = https://blogs.msdn.microsoft.com/bethmassi/2010/08/03/rapid-business-application-development-with-visual-studio-lightswitch/ | title = Rapid Business Application Development with Visual Studio LightSwitch |website=Beth Massi's blog | publisher = Microsoft| accessdate = 4 August 2010}}</ref> The second major difference was the middle tier was built and exposed using WCF RIA Services.

As of 14 October 2016, Microsoft no longer recommends LightSwitch for new application development.<ref>{{cite web | url = https://blogs.msdn.microsoft.com/lightswitch/2016/10/14/lightswitch-update/ | title = LightSwitch Update | website = Visual Studio LightSwitch Team Blog |publisher = [[Microsoft]] | accessdate = 31 May 2017}}</ref>

===Visual Studio Code===
{{Main article|Visual Studio Code}}
Visual Studio Code is a [[source code editor]], along with other features, for Linux, macOS, and Windows.<ref name=TechCrunch>{{cite news|url=https://techcrunch.com/2015/04/29/microsoft-shocks-the-world-with-visual-studio-code-a-free-code-editor-for-os-x-linux-and-windows|title=Microsoft Launches Visual Studio Code, A Free Cross-Platform Code Editor For OS X, Linux And Windows|date=29 April 2015|work=[[TechCrunch]] | first=Frederic| last=Lardinois}}</ref> It also includes support for [[debugging]] and embedded [[Git (software)|Git Control]]. It is [[open-source]],<ref name="github vscode repository">{{cite web|url=https://github.com/Microsoft/vscode/blob/master/LICENSE.txt|title=vscode licence}}</ref> and on 14 April 2016 was released as version 1.0.<ref name="Ars Technica">{{cite web|url=https://arstechnica.com/information-technology/2016/04/visual-studio-code-editor-hits-version-1-has-half-a-million-users/|title=Visual Studio Code editor hits version 1, has half a million users|date=14 April 2016| first=Peter| last=Bright}}</ref>

=== Visual Studio Team System Profiler ===
{{Main|VSTS Profiler}}
Visual Studio Team System Profiler (VSTS Profiler) is a tool to analyze the performance of .NET projects that analyzes the space and time complexity of the program.<ref>{{Cite web |url=https://msdn.microsoft.com/en-IN/library/ms182372.aspx |title=Beginners Guide to Performance Profiling |website=[[MSDN]] |publisher=Microsoft |access-date=27 December 2016}}</ref> It analyzes the code and prepares a report that includes CPU sampling, instrumentation, .NET memory allocation and [[resource contention]].<ref>{{Cite web |url=http://blog.ifourtechnolab.com/post/2016/12/26/performance-profiling-in-visual-studio1 |title=Performance Profiling in Visual Studio : VSTS Profiler |date=26 December 2016 |website=blog.ifourtechnolab.com |publisher=iFour Technolab}}</ref>

==See also==
* [[Microsoft Visual Studio Express]]
* [[Microsoft Small Basic]]
* [[AppVeyor]]
* [[Erich Gamma]]

==References==
{{Reflist|30em}}

==External links==
<!-- ======================== {{No more links}} ============================
    | PLEASE BE CAUTIOUS IN ADDING MORE LINKS TO THIS ARTICLE. Wikipedia  |
    | is not a collection of links nor should it be used for advertising. |
    |                                                                     |
    |           Excessive or inappropriate links WILL BE DELETED.         |
    | See [[Wikipedia:External links]] & [[Wikipedia:Spam]] for details.  |
    |                                                                     |
    | If there are already plentiful links, please propose additions or   |
    | replacements on this article's discussion page, or submit your link |
    | to the relevant category at the Open Directory Project (dmoz.org)   |
    | and link back to that category using the {{dmoz}} template.         |

============================ {{No more links}} ============================ -->
* {{Official website}}
* [http://www.gamasutra.com/blogs/AndreyKarpov/20121102/180783/Developing_extension_packages_for_Visual_Studio_2005200820102012_using_C_with_reallife_samples.php Developing extension packages for Visual Studio using C#]
* {{dmoz|Computers/Programming/Component_Frameworks/NET/Tools/Microsoft_Visual_Studio/}}

{{MS DevTools}}
{{Integrated development environments}}
{{.NET Framework}}
{{HTML editors}}
{{JavaScript}}

<!-- Category:Microsoft Visual Studio already encompasses [[Category:Microsoft development tools]] and [[Category:Integrated development environments]], so please don't add them, per [[WP:DIFFUSE]]. -->
[[Category:Microsoft Visual Studio| ]]
[[Category:Distributed bug tracking systems]]
[[Category:User interface builders]]
[[Category:Windows-only software]]