Screenshot of Visual Studio 2013, editing the source code of a C++ program | |
Developer(s) | Microsoft |
---|---|
Stable release | 2019 version 16.1.1 (May 24, 2019; 16 days ago[1])[±] |
Preview release | 2019 version 16.2.0 (May 25, 2019; 15 days ago[2])[±] |
Written in | C++ and C#[3] |
Operating system |
|
Available in | Chinese, Czech, English, French, German, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Russian, Spanish and Turkish[5] |
Type | Integrated development environment |
License | Freemium[6] |
Website | visualstudio.microsoft.com |
Microsoft Visual Studio 2017 15.7.6 free download standalone offline setup for Windows 32-bit and 64-bit. The Visual Studio 2017 All in One 2017 15.7 is a powerful Integrated Development Environment with support for a variety of powerful tools that help the users to develop applications for different platforms. Visual Studio Code is free and available on your favorite platform - Linux, macOS, and Windows. Download Visual Studio Code to experience a redefined code. Download setup of Visual Studio 6.0 Enterprise full working Setup. Studio 6.0 enterprise version has got some dazzling capabilities and is compatible with many distinct languages like visual c, visible fundamental c++, javascript, python and html and many others. Microsoft Project 2016 x64 Pro VL Free Download [455 MB Full] Unity Pro 5. This free download is the standalone offline setup of Visual Studio 6 Enterprise ISO Disk Image for Windows 32-bit and 64-bit. Visual Studio 6.0 Enterprise Edition Overview. Microsoft Visual Studio is the widely used Integrated Development Environment with support for almost all the popular development languages.
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is used to develop computer programs, as well as websites, web apps, web services and mobile apps. 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. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a code profiler, forms designer for building GUI applications, web designer, 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 and Git) and adding new toolsets like editors and visual designers for domain-specific languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer).
Microsoft visual studio 6 free download - Microsoft Visual Basic, Microsoft Visual Studio 2010 Ultimate, Microsoft Visual Studio 2010 Professional, and many more programs.
Visual Studio supports 36 different programming languages 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,[7]C++, C++/CLI, Visual Basic .NET, C#, F#,[8]JavaScript, TypeScript, XML, XSLT, HTML, and CSS. Support for other languages such as Python,[9]Ruby, Node.js, and M among others is available via plug-ins. Java (and J#) were supported in the past.
The most basic edition of Visual Studio, the Community edition, is available free of charge. The slogan for Visual Studio Community edition is 'Free, fully-featured IDE for students, open-source and individual developers'.
The currently supported Visual Studio version is 2019.
- 2Features
- 3Supported products
- 4Editions
- 5History
- 5.72010
- 5.82012
- 6Related products
Architecture[edit]
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 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.[10] All editors, designers, project types and other tools are implemented as VSPackages. Visual Studio uses COM to access the VSPackages. The Visual Studio SDK also includes the Managed Package Framework (MPF), which is a set of managed wrappers around the COM-interfaces that allow the Packages to be written in any CLI compliant language.[11] However, MPF does not provide all the functionality exposed by the Visual Studio COM interfaces.[12]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.[13] 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.[13] 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.[13] 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.[14] For managed code, the MPF includes wrappers for writing managed language services.[15]
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.[16] 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.[17][18] 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.[18]
Visual Studio supports running multiple instances of the environment (each with its own set of VSPackages). The instances use different registry hives (see MSDN's 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 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 Visual Studio Shell in Visual Studio 2008.[19]
Features[edit]
Code editor[edit]
Like any other IDE, it includes a code editor that supports syntax highlighting and code completion using IntelliSense for variables, functions, methods, loops, and LINQ queries.[20] IntelliSense is supported for the included languages, as well as for XML, Cascading Style Sheets, and JavaScript when developing web sites and web applications.[21][22] Autocomplete suggestions appear in a modelesslist box over the code editor window, in proximity of the editing cursor. In Visual Studio 2008 onwards, it can be made temporarily semi-transparent to see the code obstructed by it.[20] 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 collapsing code blocks and incremental search, in addition to normal text search and regex search.[23] The code editor also includes a multi-item clipboard and a task list.[23] 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 extraction, and encapsulation of class members inside properties, among others.
Visual Studio features background compilation (also called incremental compilation).[24][25] 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.[26] Background compilation was initially introduced with Microsoft Visual Basic, but has now been expanded for all included languages.[25]
Debugger[edit]
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, monitor, and debug those processes.[27] 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 dumps as well as load them later for debugging.[28] 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 breakpoints (which allow execution to be stopped temporarily at a certain position) and watches (which monitor the values of variables as the execution progresses).[29] Breakpoints can be conditional, meaning they get triggered when the condition is met. Code can be stepped over, i.e., run one line (of source code) at a time.[30] 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.[30] 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
Immediate
tool window. The parameters to the method are supplied at the Immediate window.[31]Designer[edit]
Visual Studio includes a host of visual designers to aid in the development of applications. These tools include:
![Microsoft Microsoft](/uploads/1/2/6/0/126040199/518579845.jpg)
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.[19] 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.[40]
Supported products[edit]
- Microsoft Visual C++
- Microsoft Visual C++ is Microsoft's partial implementation of the C and full implementation 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++, as of version 15.7 it conforms to C++17.[41] The C implementation of Visual Studio 2015 is still not supporting the full standard; in particular, the complex number header complex.h introduced in C99 is unsupported.
- Visual C++ supports the C++/CLI specification to write managed code, as well as mixed-mode code (a mix of 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 COM as well as the 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,[42] which are functions recognized by the compiler itself and not implemented as a library. Intrinsic functions are used to expose the SSE instruction set of modern CPUs. Visual C++ also includes the OpenMP (version 2.0) specification.[43]
- Microsoft Visual C#
- Microsoft Visual C#, Microsoft's implementation of the 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.[44]
- 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.[45][46] 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 applications and web services using ASP.NET. Either 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 provides version control, work planning and tracking, data collection, and reporting. It also includes the Team Explorer which is integrated inside Visual Studio. On 10 September 2018, Microsoft announced a rebranding of Team Foundation Server to 'Azure DevOps Server'.[47]
Previous products[edit]
numberSupported .NET
Framework versionsSupported .NET
Core versionsRelease dateVisual Studio 2019[61]Unknown16.03.5 - 4.8[62]To be announcedApril 2, 2019[63]Visual Studio 2017[64]Dev15
[citation needed]15.03.5 – 4.7[65]1.0-1.1,[66] 2.0[67]March 7, 2017Visual Studio 2015Dev14
[citation needed]14.02.0 – 4.61.0July 20, 2015Visual Studio 2013Dev12
[citation needed]12.02.0 – 4.5.2N/AOctober 17, 2013Visual Studio 2012Dev11
[citation needed]11.02.0 – 4.5.2N/ASeptember 12, 2012Visual Studio 2010Dev10,[68]Rosario[69]10.02.0 – 4.0N/AApril 12, 2010Visual Studio 2008Orcas[70]9.02.0, 3.0, 3.5N/ANovember 19, 2007Visual Studio 2005Whidbey[71]8.02.0, 3.0N/ANovember 7, 2005Visual Studio .NET 2003Everett[72]7.11.1N/AApril 24, 2003Visual Studio .NET (2002)Rainier[73]7.01.0N/AFebruary 13, 2002Visual Studio 6.0Aspen[74]6.0N/AN/AJune 1998Visual Studio 97Boston[75]5.0N/AN/AFebruary 1997
97[edit]
Microsoft first released Visual Studio (codenamed Boston,[75] for the city of the same name, thus beginning the VS codenames related to places)[75] 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] There was a single companion CD that contained the 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 MSDN Library had all been using the same 'environment', called Developer Studio.[76]
Visual Studio was also sold as a bundle with the separate IDEs used for Visual C++, Visual Basic and Visual FoxPro.[19]
6.0 (1998)[edit]
The next version, version 6.0 (codenamed Aspen, after the ski resort in Colorado),[citation needed] was released in June 1998 and is the last version to run on the Windows 9x platform.[77] 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++,[78][79] which Microsoft removed as part of a settlement with Sun Microsystems that required Microsoft Internet Explorer not to provide support for the Java virtual machine.
Visual Studio 6.0 came in two editions: Professional and Enterprise.[80] 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]
- Visual Studio Analyzer
Visual Studio was also sold as a bundle with the separate IDEs used for Visual C++, Visual Basic and Visual FoxPro.[19]
.NET (2002)[edit]
Microsoft released Visual Studio .NET (VS.NET), codenamed Rainier (for Washington'sMount Rainier),[citation needed] in February 2002 (the 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 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 and DotGNU.
This was the first version of Visual Studio to require an NT-based Windows platform.[81] The installer enforces this requirement.
Visual Studio .NET 2002 shipped in four editions: Academic, Professional, Enterprise Developer, and Enterprise Architect. Microsoft introduced 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] 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]
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.[82]
.NET 2003[edit]
In April 2003, Microsoft introduced a minor upgrade to Visual Studio .NET called Visual Studio .NET 2003, codenamed Everett (for the city of the same name).[citation needed] 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.[83]
Visual Studio .NET 2003 shipped in five editions: Academic, Standard, 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.[84]
2005[edit]
Visual Studio 2005, codenamed Whidbey (a reference to Whidbey Island in Puget Sound region),[citation needed] 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.[85][86]
Visual Studio 2005's internal version number is 8.0 while the file format version is 9.0.[83] Microsoft released Service Pack 1 for Visual Studio 2005 on 14 December 2006.[87] An additional update for Service Pack 1 that offers Windows Vista compatibility was made available on 3 June 2007.[88]
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 additionally introduces support for a new task-based build platform called Microsoft Build Engine (MSBuild) which employs a new XML-based project file format.[89] Visual Studio 2005 also includes a local web server, separate from IIS, that can host ASP.NET applications during development and testing. It also supports all SQL Server 2005 databases. Database designers were upgraded to support the 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 C++.[90] 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).[91] The 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.[92] It is significantly different from the first version, including features such as dynamic programming and support for WPF, WCF, WF, LINQ, and .NET 3.5 Framework.
2008[edit]
Visual Studio 2008,[93] and Visual Studio Team System 2008[94][95] codenamed Orcas (a reference to Orcas Island, also an island in Puget Sound region, 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 ISVs.[70] Microsoft released Service Pack 1 for Visual Studio 2008 on 11 August 2008.[96] 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.[97]
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# 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 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).[98] 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.[99] 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, iterators and algorithms that work on C++/CLImanaged objects.[100][101]
Visual Studio 2008 features include an XAML-based designer (codenamed Cider), workflow designer, LINQ to SQL designer (for defining the type mappings and object encapsulation for SQL Server data), XSLT debugger, JavaScriptIntellisense support, JavaScript Debugging support, support for UACmanifests, a concurrent build system, among others.[102] It ships with an enhanced set of UI widgets, both for Windows Forms and WPF. It also includes a multithreaded build engine (MSBuild) to compile multiple source files (and build the executable file) in a project across multiple threads simultaneously. It also includes support for compiling iconresources in PNG format, introduced in Windows Vista. An updated XML Schema designer was released separately some time after the release of Visual Studio 2008.[103]
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.[104] The threads can directly be named and flagged for easier identification from that window itself.[105] 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.[105][106] The 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 symbols and allow stepping into the BCL source during debugging.[107] As of 2010 a limited subset of the BCL source is available, with more library support planned for later.
2010[edit]
On 12 April 2010, Microsoft released Visual Studio 2010, codenamed Dev10,[68] and .NET Framework 4.[108][109]
The Visual Studio 2010 IDE was redesigned which, according to Microsoft, clears the UI organization and 'reduces clutter and complexity.'[110] The new IDE better supports multiple document windows and floating tool windows,[110] 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.[111]
The new multi-paradigmML-variant F# forms part of Visual Studio 2010.[112]
Visual Studio 2010 comes with .NET Framework 4 and supports developing applications targeting Windows 7.[110] It supports IBM DB2 and Oracle databases, in addition to Microsoft SQL Server.[110] It has integrated support for developing Microsoft Silverlight applications, including an interactive designer.[110] Visual Studio 2010 offers several tools to make parallel programming simpler: in addition to the Parallel Extensions for the .NET Framework and the Parallel Patterns Library for native code, Visual Studio 2010 includes tools for debugging parallel applications. The new tools allow the visualization of parallel Tasks and their runtime stacks.[113] Tools for profiling parallel applications can be used for visualization of thread wait-times and thread migrations across processor cores.[114] Intel and Microsoft have jointly pledged support for a new Concurrency Runtime in Visual Studio 2010[115]and Intel has launched parallelism support in Parallel Studio as an add-on for Visual Studio.[116]
The Visual Studio 2010 code editor now highlights references; whenever a symbol is selected, all other usages of the symbol are highlighted.[117] It also offers a Quick Search feature to incrementally search across all symbols in C++, C# and VB.NET projects. Quick Search supports substring matches and camelCase searches.[117] 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.[117]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.[117] Current versions of Visual Studio have a known bug which makes IntelliSense unusable for projects using pure C (not C++).[118]
Visual Studio 2010 features a new 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. Riot civil unrest free download 2017. Dynamic help containing links to related help topics based on where the developer was in the IDE has been removed in the shipping product,[119] but can be added back using a download from Microsoft.[120]
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.[121]
Ultimate 2010[edit]
Visual Studio Ultimate 2010 replaces Visual Studio 2008 Team Suite.[122] It includes new modeling tools,[123] such as the Architecture Explorer, which graphically displays projects and classes and the relationships between them.[69][124]It supports UML activity diagram, component diagram, (logical) class diagram, sequence diagram, and use case diagram.[124] 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.[125] 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.[126] Debugging with IntelliTrace causes the application to run more slowly than debugging without it, and uses more memory as additional data needs to be recorded. Microsoft allows configuration of how much data should be recorded, in effect, allowing developers to balance the speed of execution and resource usage. The Lab Management component of Visual Studio Ultimate 2010 uses virtualization to create a similar execution environment for testers and developers. The virtual machines are tagged with checkpoints which can later be investigated for issues, as well as to reproduce the issue.[127] 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.[128]
2012[edit]
Microsoft Visual Studio 2012 logo
The final build of Visual Studio 2012 was announced on 1 August 2012 and the official launch event was held on 12 September 2012.[129]
Unlike prior versions, Visual Studio 2012 cannot record and play macros and the macro editor has been removed.[130]
New features include support for WinRT and C++/CX (Component Extensions) and C++ AMP (GPGPU programming) Semantic Colorization.[131]
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.[132] 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.[133] 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.[134] '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).[135]
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:[136]
- Semantic colorization: Improved syntax coloring, various user-defined or default colors for C++ syntax such as macros, enumerations, typenames and functions.[136]
- Reference highlighting: Selection of a symbol highlights all of the references to that symbol within scope.[136]
- 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.[136]
- 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).[136]
- Member list filtering: IntelliSense uses fuzzy logic to determine which functions/variables/types to display in the list.[136]
- 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.[136]
The source code of Visual Studio 2012 consists of approximately 50 million lines of code.[137]
Interface backlash[edit]
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.[138][139]
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.[140] 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.[141] Some speculated that the root cause of the redesign was to incorporate the simplistic look and feel of Metro programs.[142] However, there exists a Windows Registry option to allow users to disable the all-caps interface.[143]
2013[edit]
The preview for Visual Studio 2013 was announced at the Build 2013 conference and made available on 26 June 2013.[144] The Visual Studio 2013 RC (Release Candidate) was made available to developers on MSDN on 9 September 2013.[145]
The final release of Visual Studio 2013 became available for download on 17 October 2013 along with .NET 4.5.1.[146] Visual Studio 2013 officially launched on 13 November 2013 at a virtual launch event keynoted by S. Somasegar and hosted on events.visualstudio.com.[147] 'Visual Studio 2013 Update 1' (Visual Studio 2013.1) was released on 20 January 2014.[148]Visual Studio 2013.1 is a targeted update that addresses some key areas of customer feedback.[149]'Visual Studio 2013 Update 2' (Visual Studio 2013.2) was released on 12 May 2014.[150]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.[151]'Visual Studio 2013 Update 4' (Visual Studio 2013.4) was released on 12 November 2014.[152]'Visual Studio 2013 Update 5' (Visual Studio 2013.5) was released on 20 July 2015.[153]
2015[edit]
Initially referred to as Visual Studio '14', the first Community Technology Preview (CTP) was released on 3 June 2014[154] and the Release Candidate was released on 29 April 2015; Visual Studio 2015 was officially announced as the final name on 12 November 2014.[155]
Visual Studio 2015 RTM was released on 20 July 2015.[156] Visual Studio 2015 Update 1 was released on 30 November 2015.[157] Visual Studio 2015 Update 2 was released on 30 March 2016.[158] Visual Studio 2015 Update 3 was released on 27 June 2016.[159]
2017[edit]
Microsoft Visual Studio 2017 logo
Initially referred to as Visual Studio '15', it was released on 7 March 2017.[160] The first Preview was released on 30 March 2016.[161] Visual Studio '15' Preview 2 was released 10 May 2016.[162][163] Visual Studio '15' Preview 3 was released on 7 July 2016.[164][165] Visual Studio '15' Preview 4 was released on 22 August 2016.[166][167] Visual Studio '15' Preview 5 was released on 5 October 2016.[168]
As of April 2016, Visual Studio is making the EthereumSolidity language available to developers.[169]
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.[170]
On 16 November 2016, 'Visual Studio 2017' was announced as the final name,[171] and Visual Studio 2017 RC was released.[172]
On 7 March 2017, Visual Studio 2017 was released for general availability.[172]
On 14 March 2017, first fix was released for Visual Studio 2017 due to failures during installation or opening solutions in the first release.[172]
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 Git vulnerability with submodules (CVE 2017-1000117).
On October 10, 2017, Visual Studio 15.4 was released.[173]
On December 4, 2017, Visual Studio 15.5 was released. This update contained major performance improvements, new features, as well as bug fixes.[174]
On March 6, 2018, Visual Studio 15.6 was released. It includes updates to unit testing and performance.[175]
On May 7, 2018, Visual Studio 15.7 was released. It included updates across the board including, the installer, editor, debugger among others. Almost all point releases, the latest of which is 15.7.6 released August 2, 2018, include security updates. With the release of Visual Studio 2017 15.7, Visual C++ now conforms to the C++17 standard.[41]
On 20 September 2018, Visual Studio 15.8.5 was released. Tools for Xamarin now supports Xcode 10.[176]
Visual Studio 2017 offers new features like support for EditorConfig (a coding style enforcement framework), NGen support, .NET Core and Docker toolset (Preview), and Xamarin 4.3 (Preview).[172] It also has a XAML Editor, improved IntelliSense, live unit testing, debugging enhancement and better IDE experience and productivity.[177]
2019[edit]
On June 6, 2018 Microsoft announced Visual Studio 2019 (version 16).[61]
On December 4, 2018 Visual Studio 2019 Preview 1 was released. [178] On January 24, 2019 Visual Studio 2019 Preview 2 was released. [179] On February 13, 2019 Visual Studio 2019 Preview 3 was released. [180]
On February 27, 2019 Visual Studio 2019 RC was released. [181]
It is generally available (GA) since April 2nd, 2019 and available for download. [182]
Related products[edit]
Azure DevOps Services[edit]
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 the on-premises Team Foundation Server by making it available on the Internet and implementing a rolling release model.[183][184] Customers could use Azure portal to subscribe to Visual Studio Online. Subscribers receive a hosted Git-compatible version control system, a load-testing service, a telemetry service and an in-browser code editor codenamed 'Monaco'.[185] During the Connect(); 2015 developer event on 18 November 2015, Microsoft announced that the service was rebranded as 'Visual Studio Team Services (VSTS)'.[186] On 10 September 2018, Microsoft announced another rebranding of the service, this time to 'Azure DevOps Services'.[47]
Microsoft offers Stakeholder, Basic, and Visual Studio subscriber access levels for Azure DevOps Services. The Basic plan is free of charge for up to five users. Users with a Visual Studio subscription can be added to a plan with no additional charge.[187]
Visual Studio Application Lifecycle Management[edit]
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).[188] 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.[189]
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[123][190] Visual Studio ALM with the Visual Studio 2010 (codenamed 'Rosario') release.[191]
Visual Studio Team Services debuted as Visual Studio Online in 2013 and was renamed in 2015.[192]
Visual Studio Lab Management[edit]
Visual Studio Lab Management is a software development tool developed by Microsoft for software testers to create and manage virtual environments. Lab Management extends the existing Visual Studio Application Lifecycle Management platform to enable an integrated Hyper-V based test lab. Since Visual Studio 2012, it is already shipped as a part of it; and, can be set up after Team Foundation Server and SCVMM are integrated.[193]
Visual Studio LightSwitch[edit]
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 3-tier: the user interface runs on either Microsoft Silverlight or HTML 5 client,[194] or as a SharePoint 2013 app;[195] the logic and. docs.microsoft.com. Retrieved 25 May 2019.
|first1=
missing |last1=
(help)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.
External links[edit]
- Official website
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Microsoft_Visual_Studio&oldid=898530664'
-->| Developer Community| System Requirements| Compatibility| Distributable Code| License Terms| Blogs| Known Issues |
Click a button to download the latest version of Visual Studio 2017. For instructions on installing and updating Visual Studio 2017, see Update Visual Studio 2017 to the most recent release. Also, see instructions on how to install offline.
Visit the visualstudio.com/downloads page to download other Visual Studio 2017 products.
What's New in 15.9
Visual Studio 2017 version 15.9 Releases
- June 11, 2019 -- Visual Studio 2017 version 15.9.13 Servicing Update
- May 14, 2019 -- Visual Studio 2017 version 15.9.12 Servicing Update
- April 02, 2019 -- Visual Studio 2017 version 15.9.11 Servicing Update
- March 25, 2019 -- Visual Studio 2017 version 15.9.10 Servicing Update
- March 12, 2019 -- Visual Studio 2017 version 15.9.9 Servicing Update
- March 05, 2019 -- Visual Studio 2017 version 15.9.8 Servicing Update
- February 12, 2019 -- Visual Studio 2017 version 15.9.7 Servicing Update
- January 24, 2019 -- Visual Studio 2017 version 15.9.6 Servicing Update
- January 08, 2019 -- Visual Studio 2017 version 15.9.5 Servicing Update
- December 11, 2018 -- Visual Studio 2017 version 15.9.4 Servicing Update
- November 28, 2018 -- Visual Studio 2017 version 15.9.3 Servicing Update
- November 19, 2018 -- Visual Studio 2017 version 15.9.2 Servicing Update
- November 15, 2018 -- Visual Studio 2017 version 15.9.1 Servicing Update
- November 13, 2018 -- Visual Studio 2017 version 15.9 Minor Release
Important
Visual Studio 2017 version 15.9 Security Advisory Notices
- May 10, 2019 -- Visual Studio 2017 version 15.9.12 Servicing Update
- March 12, 2019 -- Visual Studio 2017 version 15.9.9 Servicing Update
- February 12, 2019 -- Visual Studio 2017 version 15.9.7 Servicing Update
- January 08, 2019 -- Visual Studio 2017 version 15.9.5 Servicing Update
- December 11, 2018 -- Visual Studio 2017 version 15.9.4 Servicing Update
Visual Studio 2017 version 15.9.13
released on June 11, 2019
Issues Fixed in 15.9.13
Download torrent kaamelott dies iron. These are the customer-reported issues addressed in 15.9.13:
- Fixed a bug that caused Code Analysis to stop running on some C++ projects.
- Fixed a bug in the Schema Compare Tool where adding tables with an empty schema failed but was shown as successful.
- Fixed a TypeScript build issue when the selected language version is lower than the latest installed.
- Fixed a Database unresolved reference to object error.
- Improved performance issues on loading Visual Studio.
- Fixed known issue: No snapshot created for C++ native code in Memory Usage tool in the Diagnostic Tools window while debugging.
Visual Studio 2017 version 15.9.12
released on May 14, 2019
Issues Fixed in 15.9.12
These are the customer-reported issues addressed in 15.9.12:
- Access violation C++ /CLI 15.9.5 ISO C++ Latest Draft Standard since 15.9.5.
- An error occurred loading this property page (CSS & JSON).
- Visual Studio 2017 crashing when editing package.json.
- Opening package.json locks up Visual Studio.
- PGO Code Gen Bug - Vectorized instruction accessing memory OOB.
- Bad code gen in recursive bucket split routine.
- Compiler optimization bug in 15.8.9.
- Fixed a linker error LNK4020 when using PCH, /Zi, and /GL in distributed build systems, such as IncrediBuild. The C++ compiler backend now correctly associates CIL OBJs with their corresponding compiler generated PDB when generating debug info for cross-module inlining.
Security Advisory Notices
Visual Studio 2017 version 15.9.11
released on April 02, 2019
Issues Fixed in 15.9.11
These are the customer-reported issues addressed in 15.9.11:
- Access violation C++ /CLI 15.9.5 ISO C++ Latest Draft Standard since 15.9.5.
- PGO Code Gen Bug - Vectorized instruction accessing memory OOB.
- Visual Studio completely freezes when editing package.json.
- An error occurred loading this property page (CSS & JSON).
- Clicking on a web app URL in the Azure activity log now successfully publishes a Cloud Service Project.
- You can now publish to a Function app even if you are not logged into the account that contains the function app.
- We have fixed an unhandled exception in the HTML editor.
- We have updated the scaffolding package to install Microsoft.VisualStudio.Web.CodeGeneration.Design package version 2.1.9 for .NET Core 2.1 and version 2.2.3 for .NET Core 2.2.
- We have implemented a C++ compiler fix to correct exception handling support for code using setjmp/longjmp in Release mode.
- We have implemented a C++ linker fix regarding information in PDB where the incorrect module info could result in heap corruption when producing a stripped PDB file either by PDBCopy.exe or by link.exe when option /PDBSTRIPPED is specified.
- We have corrected dual signing of the ARM64 Visual C++ Redistributable installer.
Visual Studio 2017 version 15.9.10
released on March 25, 2019
Issues Fixed in 15.9.10
These are the customer-reported issues addressed in 15.9.10:
- We have fixed an issue with debugging using Docker when a web proxy is configured.
- In debugging using Docker, you will now experience improved error handling for failures related to drive sharing configuration (for example, expired credentials).
Visual Studio 2017 version 15.9.9
released on March 12, 2019
Issues Fixed in 15.9.9
These are the customer-reported issues addressed in 15.9.9:
- We have fixed an issue with deploying resource group projects when a subscription owner's name contains an apostrophe.
- SSDT: We fixed a crash in the SSIS Foreach Loop container.
- A few .NET native for UWP customer issues were fixed in .NET native tools 2.2 (UWP 6.2.4).
- We have corrected dual signing of Visual C++ Redistributable installers.
Security Advisory Notices
- A remote code execution vulnerability exists when the Visual Studio C++ Redistributable Installer improperly validates input before loading dynamic link library (DLL) files.
- Unity Editor Remote Code Execution Vulnerability.
- .NET Core NuGet Tampering Vulnerability.
Visual Studio 2017 version 15.9.8
released on March 05, 2019
Issues Fixed in 15.9.8
These are the customer-reported issues addressed in 15.9.8:
- ModelBus-enabled text transformation fails on 15.8.
- SSDT: Fix to improve performance of loading solutions with multiple projects.
- Vulnerabilities in the OpenJDK Platform binary.
Visual Studio 2017 version 15.9.7
released on February 12, 2019
Issues Fixed in 15.9.7
![Studio Studio](https://media.phpnuke.org/000/976/003/1e2_b16_580_580-microsoft-visual-studio-3.jpg)
These are the customer-reported issues addressed in 15.9.7:
- Crashes when expanding variables!.
- /DEBUG:FASTLINK + C7 + PCH crashes debugger.
- Native C++ application crashes because of stack corruption with VS 2017 15.9.2.
- Incorrect Release Mode code.
- Xamarin Unobserved Task Exception WebRequest.
- Link /SOURCELINK option seems to do nothing. This fixes Source Link for Managed C++ Debugging.
- Fixed an issue with corruption of AVX/MPX/AVX512 registers while Debugging.
- Update of Microsoft.VCLibs.140.00.UWPDestkop framework packages for C++ UWP DesktopBridge applications adding support for ARM64.
- Corrected incorrect version of VCToolsRedistVersion in Microsoft.VCToolsVersion.default.props.
- Corrected unsigned embedded dll for VC Redist installers.
- SSDT/Web Tools: We fixed an issue where SQL LocalDB was not installed on Polish, Turkish, and Czech locales.
- SSDT: We fixed an issue affecting SQL Server Analysis Services (Method not found exception when clicking on UI).
- SSDT: We fixed an accessibility issue which was causing the contents of a table not to be visible in the result window when using High-Contrast mode.
Security Advisory Notices
- WorkflowDesigner XOML deserialization allows code execution.
- .NET Framework and Visual Studio Spoofing Vulnerability.
Visual Studio 2017 version 15.9.6
released on January 24, 2019
Issues Fixed in 15.9.6
These are the customer-reported issues addressed in 15.9.6:
- Installation failures of the Unity Editor component in China.
- Starting a new nanoFramework project from a template.
- Deployment errors after VS2017 update.
- Android Deploy failed - Error ADB0010.
- Error in German translation: info bar 'session closed unexpectedly'.
- Visual Studio 2017 create offline layout problem: Failed to load from stream for non-ENU layouts.
- Extension auto-update can leave extension disabled.
Visual Studio 2017 version 15.9.5
released on January 08, 2019
Issues Fixed in 15.9.5
These are the customer-reported issues addressed in 15.9.5:
- VSX1000: No enough information has been provided to MSBuild in order to establish a connection to a Remote Server.
- Visual C++ 2017 Redistributable for ARM64 is not available via visualstudio.com.
- VC Runtime Redistributable Update for VS 15.9 deletes Registry Key. This fix may have an increased chance of requiring a reboot of the machine in order to install an updated VC++ Redistributable package.
- Incorrect codegen in managed c++ with List to List assignment.
- Can't connect to mac build host after Visual Studio 15.9.4 update.
- Resource directories missed in incremental builds with
AndroidAarLibrary
items. - Lots of external assembly references - JNI ERROR (app bug): local reference table overflow (max=512).
- The Unity Editor has been updated to 2018.3. For more information, please visit the Unity website.
- SSDT: We enabled SQL projects to build schemas that have non-clustered columnstore indexes on an indexed views.
- SSDT: We fixed a significant performance issue in the schema compare tool when generating a script.
- SSDT: We fixed the schema drift detection logic in the schema compare tool which forced a new comparison to reenable scripting and publishing actions.
Security Advisory Notices
- A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ constructs.
Visual Studio 2017 version 15.9.4
released on December 11, 2018
Issues Fixed in 15.9.4
These are the customer-reported issues addressed in 15.9.4:
- Visual Studio 15.9 duplicate loads open files on solution reload.
- All users can now connect to on-premise TFS servers through Team Explorer.
- Visual Studio 15.8.3 no longer expands metadata in ItemDefinitionGroup for project-defined items during GUI builds (worked in Visual Studio 15.8.2).
- Visual Studio has multiple tabs for the same file.
- System.ArgumentException: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)).
- LNK4099 PDB not found.
- Asset Catalog empty.
- /analyze fails for C++ code using /ZW.
- C++ compiler code optimization bug.
- Xamarin.iOS can't select image asset for Image View.
- iOS projects referencing a shared project containing image assets in an asset catalog fail to load on windows.
- Image not populating on iOS splashscreen in VS 15.8.6.
- Possible bad codegen on union/bitfield assignment in VS2017 15.8.
- Fix C# UWP Store 1201 Submission Issue.
- Fix C# UWP package creation error APPX1101: Payload contains two or more files with the same destination path 'System.Runtime.CompilerServices.Unsafe.dll'.
- Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions..' when building a Xamarin.iOS project.
- Redirecting to a relative url doesn't work when using AndroidClientHandler.
- Debug information for typedefs of unnamed enums compiled with the C compiler is now restored.
- The spectre-mitigated x86 version of delayimp.lib is now built with /Qspectre mitigations enabled.
- Changes were made to how Asset Catalogs in Xamarin.iOS projects are loaded in order to reduce solution load time.
- We have updated Xamarin.Forms templates to use the latest version.
- We have fixed an issue with ASP.NET Core Web Applications being debugged through Kestrel that would show the error message 'Unable to configure HTTPS endpoint. No server certificate was specified..'.
- Enabling the AppInsights site extension in App Service from Visual Studio now happens through the use of specific Application Settings.
Security Advisory Notices
- An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles certain file operations.
Visual Studio 2017 version 15.9.3
released on November 28, 2018
Issues Fixed in 15.9.3
These are the customer-reported issues addressed in 15.9.3:
- Visual Studio 15.9 - duplicate loads open files on solution reload.
- Issues with reloading and IntelliSense with Unity projects and Visual Studio 2017 15.9.x.
Visual Studio 2017 version 15.9.2
released on November 19, 2018
Issues Fixed in 15.9.2
These are the customer-reported issues addressed in 15.9.2:
- MFC EXE (binary) size is 5 times bigger in VS 15.8 (_MSC_VER = 1915).
- Key 'OPENSSH' is not supported.
- Windows magnifier can no longer track keyboard cursor.
- Analysis fails with immediately-invoked lamba in while loop.
- Xamarin iOS designer not working with 15.9 and Xamarin.iOS 12.2.1.10.
- We improved the reliability of incremental linking for large C++ projects.
- LNK2001 'unresolved external symbol' errors for certain vector deleting destructors will now be resolved.
- Compiler execution time has been improved for code that makes heavy use of chained, inline functions involving lambdas or local classes as parameter or return types.
Visual Studio 2017 version 15.9.1
released on November 15, 2018
Issues Fixed in 15.9.1
These are the issues addressed in 15.9.1:
- Fixed a bug where Visual Studio would fail to build projects using the Microsoft Xbox One XDK.
Details of What's New in 15.9.1
Universal Windows Platform Development SDK
The Windows 10 October 2018 Update SDK (build 17763) is now the default selected SDK for the Universal Windows Platform development workload.
Summary of Notable New Features in 15.9
- You can now import and export an installation configuration file that specifies which workloads and components should be installed with an instance of Visual Studio.
- We have improved the debugging experience for NuGet packages using the new symbol package format (.snupkg).
- Step back in debugger is now available in C++ for Enterprise customers.
- C++ IntelliSense now responds to changes in the remote environment for both CMake and MSBuild projects targeting Linux.
- We have made updates to UWP Desktop Bridge framework packages and added support for ARM64 C++ Native Desktop scenarios.
- We added support for the range-v3 library with the MSVC 15.9 compiler.
- We fixed several bugs in the F# compiler and F# tools.
- Language service support for new TypeScript features for semantic file renaming and project references.
- Improved Node.js development by updating Vue.js templates and adding support for unit testing using the Jest framework.
- We added SharePoint 2019 project templates, so you can migrate existing SharePoint 2013 and 2016 projects to SharePoint 2019.
- Visual Studio Tools for Xamarin now supports Xcode 10.
- We made improvements to the Xamarin.Android build performance.
- We have added and improved features for Universal Windows Platform developers, including ARM64 support, the latest preview SDK, better debugging of Desktop Bridge applications, and XAML Designer improvements.
- Substantial improvements were made to the experience of using authenticated package feeds.
- There is now support for lock file to enable repeatable restore for PackageReference based projects.
- We have added support for the new license format for NuGet packages.
- We have introduced NuGet client policies in Visual Studio which enables you to lock down environments such that only trusted packages can be installed.
- We made the use of .NET Core within Visual Studio more predictable.
Top Issues Fixed in 15.9
- No way to change 'Find All References' background color.
- 'Visual C++ Resource Editor Package' load failed.
- VS2017 v15.8 Build does not start if XAML files are not manually saved first.
- Installation failed - manifest signature verification failed.
- Update 15.8.6 breaks Installer Projects.
- Scrolling up with the arrow key causes Visual Studio to page up.
- After updating to 15.8.1, data tip does not show when debugging.
- System.InvalidProgramException: Common Language Runtime detected an invalid program.
- Solution Explorer does not remain pinned after closing Visual Studio.
- Navigation bar in editor has trouble handling long method names.
- Editor Package load failure error on startup of Blend.
See all customer-reported issues fixed in Visual Studio 2017 version 15.9.
Details of What's New in 15.9
Visual Studio 2017 version 15.9.0
released on November 13, 2018
New Features in 15.9
Install
We made it easier to keep your installation settings consistent across multiple installations of Visual Studio. You can now use the Visual Studio Installer to export a .vsconfig file for a given instance of Visual Studio. This file will contain information about what workloads and components you have installed. You can then import this file to add these workload and component selections to another installation of Visual Studio.
Debugging
We have added support for consuming the new portable-pdb based symbol package format (.snupkg). We have added tooling to make it easy to consume and manage these symbol packages from sources like the NuGet.org symbol server.
C++
- We've added the 'step back' feature in the debugger for C++ in the Visual Studio Enterprise Edition. Step back enables you to go back in time to view the state of your application at a previous point in time.
- C++ IntelliSense now responds to changes in the remote environment for both CMake and MSBuild projects targeting Linux. As you install new libraries or change your CMake projects, C++ IntelliSense will automatically parse the new headers files on the remote machine for a complete and seamless C++ editing experience.
- We've updated the UWP Desktop Bridge framework packages to match the latest in the Windows Store for all supported architectures, including ARM64.
- In addition to fixing 60 blocking bugs, we have added support for the range-v3 library with the MSVC 15.9 compiler, available under /std:c++17 /permissive-.
- The retail VCLibs framework package in Visual Studio has been updated to match the latest available version in the UWP Store.
- Full support is now available for ARM64 C++ Native Desktop scenarios, including VC++ 2017 Redistributable.
- We implemented the shortest round-trip decimal overloads of floating-point to_chars() in C++17's charconv header. For scientific notation, it is approximately 10x as fast as sprintf_s() '%.8e' for floats, and 30x as fast as sprintf_s() '%.16e' for doubles. This uses Ulf Adams' new algorithm, Ryu.
- A list of improvements to the standards conformance of the Visual C++ compiler, which potentially require source changes in strict conformance mode, can be found here.
- We have deprecated the C++ Compiler /Gm switch. Consider disabling the /Gm switch in your build scripts if it's explicitly defined. Alternatively, you can also safely ignore the deprecation warning for /Gm as it will not be treated as error when using 'Treat warnings as errors' (/WX).
F#
F# Compiler
- We fixed a bug where extension methods that take
byref
values could mutate an immutable value. - We improved the compile error information for overloads on
byref
/inref
/outref
, rather than displaying the previously obscure error. - Optional Type Extensions on
byref
s are now disallowed entirely. They could be declared previously, but were unusable, resulting in a confusing user experience. - We fixed a bug where
CompareTo
on a struct tuple and causing a type equivalence with an aliased struct tuple would result in a runtime exception. - We fixed a bug where use of
System.Void
in the context of authoring a Type Provider for .NET Standard could fail to find theSystem.Void
type at design-time. - We fixed a bug where an internal error could occur when a partially applied Discriminated Union constructor is mismatched with an annotated or inferred type for the Discriminated Union.
- We modified the compiler error message when attempting to take an address of an expression (such as accessing a property) to make it more clear that it violates scoping rules for
byref
types. - We fixed a bug where your program could crash at runtime when partially applying a
byref
type to a method or function. An error message will now display. - We fixed an issue where an invalid combination of a
byref
and a reference type (such asbyref<int> option
) would fail at runtime and not emit an error message. We now emit an error message.
F# Tools
- We resolved an issue where metadata for F# assemblies built with the .NET Core SDK was not shown in file properties on Windows. You can now see this metadata by right-clicking an assembly on Windows and selecting Properties.
- We fixed a bug where use of
module global
in F# source could cause Visual Studio to become unresponsive. - We fixed a bug where extension methods using
inref<'T>
would not show in completion lists. - We fixed a bug where the TargetFramework dropdown in Project Properties for .NET Framework F# projects was empty.
- We fixed a bug where creating a new F# project targeting .NET Framework 4.0 would fail.
F# Open Source Repository
The VisualFSharpFull project is now set as the default startup project, eliminating the need to manually set that before debugging. Thanks, Robert Jeppesen!
JavaScript and TypeScript Language Service Support
- We added refactoring to fix up references to a file after it has been renamed. We also added support for project references, letting you split your TypeScript project up into separate builds that reference each other.
- We updated to the latest Vue CLI 3.0 and improved linting in Vue.js template files. You can also write and run unit tests using the Jest framework.
- We have added support for TypeScript 3.1.
SharePoint 2019 Support
We added new templates that allow you to create projects for SharePoint 2019. You will have the ability to migrate existing SharePoint projects from both SharePoint 2013 and SharePoint 2016 to the new project template.
Visual Studio Tools for Xamarin
Visual Studio Tools for Xamarin now supports Xcode 10, which allows you to build and debug apps for iOS 12, tvOS 12, and watchOS 5. See how to get ready for iOS 12and our introduction to iOS 12for more details on the new features available.
Initial Xamarin.Android Build Performance Improvements
Xamarin.Android 9.1 includes initial build performance improvements. See our Xamarin.Android 15.8 vs. 15.9 build performance comparison for more details.
Tools for Universal Windows Platform Developers
- The latest Windows 10 SDK (build 17763) is included as an optional component in the Universal Windows Platform development Workload.
- We added support for creating .MSIX packages for both the Universal Windows Platform projects, as well as in the Windows Application Packaging Project template. To create an .MSIX package, the minimum version of your application must be the latest Windows 10 SDK (build 17763).
- You can now build ARM64 UWP applications. For .NET UWP applications, only .NET Native is supported for ARM64, and you must set the Minimum Version of your application to the Fall Creators Update (Build 16299) or higher.
- We made improvements to the F5 (Build + Deploy) speed for Universal Windows Platform applications. This will be most noticeable for deployments to remote targets using Windows authentication, but will impact all other deployments as well.
- Developers now have the option to specify Control Display Options when using the XAML Designer while building UWP applications targeting the Windows 10 Fall Creators Update (build 16299) or later. Selecting 'Only Display Platform Controls' prevents the designer from executing any custom control code to improve reliability of the designer.
- The XAML designer now automatically replaces controls that throw with catchable exceptions with fallback controls, rather than having the designer crash. Fallback controls have a yellow border to cue in developers that the control has been replaced at design time.
- The Windows Application Packaging project now supports debugging background process using the Core CLR debugger type.
NuGet
NuGet Credential Provider Improvements
This release substantially improves the experience of using authenticated package feeds, especially for Mac and Linux users:
- Visual Studio, MSBuild, NuGet.exe, and .NET now support a new Credential Provider plugin interface, which can be implemented by private package hosts like Azure Artifacts. Previously, only NuGet.exe and Visual Studio accepted Credential Providers.
- Visual Studio editions (including the Build Tools edition) now deliver the Azure Artifacts Credential Provider with certain workloads, so that you can easily use Azure Artifacts feeds in the course of your development.To use these improvements, install the NuGet package manager or NuGet targets and build tasks components, or the .NET Core workload.
NuGet Package Manager Improvements
- NuGet now enables locking the full package closure of PackageReference based projects, thereby enabling repeatable restore of packages.
- The Visual Studio NuGet package manager UI now surfaces the license information for packages that use the new license format. The new license format embeds the license information as part of the package in the form of an SPDX expression or a license file.
NuGet Security
We have introduced NuGet Client Policies which allow you to configure package security constraints. This means you can lock down environments so only trusted packages can be installed by:
- Disallowing the installation of unsigned packages.
- Defining a list of trusted signers based on the author signature.
- Defining a list of trusted NuGet.org package owners based on the metadata in the repository signature.
.NET Core Tools for Visual Studio
Starting with this release, the .NET Core tools for Visual Studio will now default to using only the latest stable version of a .NET Core SDK that is installed on your machine for GA releases of Visual Studio. For future previews, the tools will use only preview .NET Core SDKs.
Visual Studio 2017 version 15.9 Security Advisory Notices
Visual Studio 2017 version 15.9.12 Service Release-- released on May 14, 2019
CVE-2019-0727 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability
An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly performs certain file operations. An attacker who successfully exploited this vulnerability could delete files in arbitrary locations. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by securing locations the Diagnostics Hub Standard Collector performs file operations in.
Visual Studio 2017 version 15.9.9 Service Release-- released on March 12, 2019
CVE-2019-0809 Visual Studio Remote Code Execution Vulnerability
A remote code execution vulnerability exists when the Visual Studio C++ Redistributable Installer improperly validates input before loading dynamic link library (DLL) files. An attacker who successfully exploited the vulnerability could execute arbitrary code in the context of the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. To exploit the vulnerability, an attacker must place a malicious DLL on a local system and convince a user to execute a specific executable. The security update addresses the vulnerability by correcting how the Visual Studio C++ Redistributable Installer validates input before loading DLL files.
CVE-2019-9197 Unity Editor Remote Code Execution Vulnerability
A remote code execution vulnerability exists in the Unity Editor, a 3rd party software that Visual Studio offers to install as part of the Game Development with Unity workload. If you've installed Unity from Visual Studio, please make sure to update the version of Unity you're using to a version that addresses the vulnerability as described in the CVE.The Visual Studio installer has been updated to offer to install a Unity Editor version which addresses the vulnerability.
CVE-2019-0757 .NET Core NuGet Tampering Vulnerability
A tampering vulnerability exists in NuGet software when executed in a Linux or Mac environment. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that an attacker can login as any other user on that machine. At that point, the attacker will be able to replace or add to files that were created by a NuGet restore operation in the current users account.
.NET Core updates have released today and are included in this Visual Studio update. The security update addresses the vulnerability by correcting how NuGet restore creates file permissions for all files extracted to the client machine. Details about the packages can be found in the .NET Core release notes.
Visual Studio 2017 version 15.9.7 Service Release-- released on February 12, 2019
CVE-2019-0613 WorkflowDesigner XOML deserialization allows code execution
A XOML file referencing certain types could cause random code to be executed when the XOML file is opened in Visual Studio.There is now a restriction on what types are allowed to be used in XOML files. If a XOML file containing one ofthe newly unauthorized types is opened, a message is displayed explaining that the type is unauthorized.
If it is known that the XOML file being opened does not cause security issues, you can disable the check forunauthorized types by adding a key to the
<appSettings>
section of the devenv.exe.config file as follows:This appSetting value completely disables the type checking in the XOML serializer. If this value is 'true', it takes precedence over the other new appSetting.
If you only want to disallow a few specific types, but allow all other types, your needto make the following changes to your devenv.exe.config file:
This will allow all of the types are were unauthorized by default. To mark specific types as unauthorizedyou must also add these changes to the devenv.exe.config file:
The above changes will only mark the type System.Activities.Presentation.WorkflowDesigner in the assemblySystem.Activities.Presentation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 as unauthorized.To mark other types as unauthorized add similar entries for those other types.
CVE-2019-0657 .NET Framework and Visual Studio Spoofing Vulnerability
.NET Core updates have released today and are included in this Visual Studio update. This release addresses security and other important issues. Details can be found in the .NET Core release notes.
Visual Studio 2017 version 15.9.5 Service Release-- released on January 08, 2018
CVE-2019-0546 Visual Studio Remote Code Execution Vulnerability
A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ constructs. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. The security update addresses the vulnerability by correcting how the Visual Studio C++ compiler handles certain C++ constructs.
Visual Studio 2017 version 15.9.4 Service Release-- released on December 11, 2018
CVE-2018-8599 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability
An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles certain file operations. An attacker who successfully exploited this vulnerability could gain elevated privileges. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by ensuring the Diagnostics Hub Standard Collector Services properly impersonates file operations.
Fixed Issues
See all customer-reported issues fixed in Visual Studio 2017 version 15.9.
Known Issues
See all existing known issues and available workarounds in Visual Studio 2017 version 15.9.
Feedback
We would love to hear from you! For issues, let us know through the Report a Problem option in the upper right-handcorner of either the installer or the Visual Studio IDE itself. The icon is located in the upper right-hand corner.You can make a product suggestion or track your issues in the Visual Studio Developer Community, where you can ask questions, find answers, and propose new features.You can also get free installation help through our Live Chat support.
Blogs
Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.
Visual Studio 2017 Release Notes History
For more information relating to past versions of Visual Studio 2017, see the Visual Studio 2017 Release Notes History page.