Microsoft Visual Studio 2008 Professional Edition (Retail Edition NOT OEM)
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, 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 Azure DevOps client: Team Explorer).
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,[8] C++, C++/CLI, Visual Basic .NET, C#, F#,[9] JavaScript, TypeScript, XML, XSLT, HTML, and CSS. Support for other languages such as Python,[10] 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".
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.[11] 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.[12] However, MPF does not provide all the functionality exposed by the Visual Studio COM interfaces.[13] 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.[14] 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.[14] 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.[14] 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.[15] For managed code, the MPF includes wrappers for writing managed language services.[16]
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.[17] 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.[18][19] 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.[19]
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.[20]
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.[21] IntelliSense is supported for the included languages, as well as for XML, Cascading Style Sheets, and JavaScript when developing web sites and web applications.[22][23] Autocomplete suggestions appear in a modeless list 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.[21] 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.[24] The code editor also includes a multi-item clipboard and a task list.[24] 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).[25][26] 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.[27] Background compilation was initially introduced with Microsoft Visual Basic, but has now been expanded for all included languages.[26]
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.[28] 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.[29] 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).[30] 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.[31] 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.[31] 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.[32]
Visual Studio includes a host of visual designers to aid in the development of applications. These tools include:
CTRL+TAB
.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, 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.[13] 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 COM and can be created in any COM-compliant languages.[13] Packages are created using the Visual Studio 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 APIs as well as a managed API to accomplish these tasks. However, the managed API isn't as comprehensive as the unmanaged one.[13] Extensions are supported in the Standard (and higher) versions of Visual Studio 2005. 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.[20] 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.[41]
Microsoft Visual Studio is available in the following editions or SKUs:[55]
The Community edition was announced on 12 November 2014, as a new free version, with similar 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. Individual developers have no restrictions on their use of the Community edition. The following uses also allow unlimited usage: contributing to Open Source projects, academic research, in a classroom learning environment and for developing and testing device drivers for the Windows operating system. All other use by an organization depends on whether you are classified as an Enterprise (more than 250 employees / 1 Million+ in revenue, per Microsoft). Non-Enterprises may use up to 5 copies without restriction, user number 6 and higher require a commercial license; Enterprise organizations require a commercial license for use outside of the noted exceptions.[56][57] Visual Studio Community is oriented towards individual developers and small teams.[58][59]
As of Visual Studio 2010, the Professional edition is the entry level commercial edition of Visual Studio. (Previously, a more feature restricted Standard edition was available.)[60] 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 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.
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.
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 Azure DevOps. It does not include support for development or authoring of tests.[55]
The first version of Visual Studio was Visual Studio 97.[61] Before that, Visual Basic, Visual C++, Visual FoxPro and Visual SourceSafe were sold as separate products.
Product name | Code name | Release date | Version number |
Latest Update | Latest Update date | Support Ends | Supported .NET Framework |
Supported .NET Core |
---|---|---|---|---|---|---|---|---|
Visual Studio 2019 | Dev16 | 2019-04-02[62] | 16.0 | 16.4.1 | 2019-11-12 | April 10, 2029[65] | 3.5 - 4.8[66] | 2.1, 2.2[66], 3.0[67], 3.1[68] |
Visual Studio 2017 | Dev15[69] | 2017-03-07[70] | 15.0 | 15.9.18[71] | 2019-12-10 | April 13, 2027[72] | 3.5 - 4.7.2[73] | 1.0-1.1[74], 2.0[75], 2.1 |
Visual Studio 2015 | Dev14[76] | 2015-07-20[77][78] | 14.0 | Update 3[79] | 2016-06-27 | October 14, 2025[80] | 2.0 - 4.6.1 | 1.0 |
Visual Studio 2013 | Dev12[76] | 2013-10-17[81][82] | 12.0 | Update 5[77] | 2015-07-20 | April 9, 2024[83] | 2.0 - 4.5.1 | N/A |
Visual Studio 2012 | Dev11[76] | 2012-09-12[84][85][86] | 11.0 | Update 5[87] | 2015-08-24 | January 10, 2023[88] | 2.0 - 4.5 | N/A |
Visual Studio 2010 | Dev10[89], Rosario[90] | 2010-04-12[91][92] | 10.0 | Service Pack 1[93][94] | 2011-03-10 | July 14, 2020[95] | 2.0 - 4.0 | N/A |
Visual Studio 2008 | Orcas[96] | 2007-11-19[97] | 9.0 | Service Pack 1[98] | 2008-08-11 | April 10, 2018[99] | 2.0, 3.0, 3.5 | N/A |
Visual Studio 2005 | Whidbey[100] | 2005-11-07[101] | 8.0 | Service Pack 1[102] | 2006-12-15 | April 12, 2016[103] | 2.0 | N/A |
Visual Studio .NET 2003 | Everett[104] | 2003-04-24[105] | 7.1 | Service Pack 1[106] | 2006-08-15 | October 14, 2013[107] | 1.1 | N/A |
Visual Studio .NET (2002) | Rainier[108] | 2002-02-13[109] | 7.0 | Service Pack 1[110] | 2005-03-08 | July 14, 2009[111] | 1.0 | N/A |
Visual Studio 6.0 | Aspen[112] | 1998-06[113][114] | 6.0 | Service Pack 6[115] | 2004-03-25 | September 30, 2005[116][117] | N/A | N/A |
Visual Studio 97 | Boston[118] | 1997-02[119][120] | 5.0 | N/A | N/A | June 30, 2003[121][122] | N/A | N/A |
Please confirm what you required and we would forward price details and related information.
Shipping and Personal Collection
All customers are welcome to collect in person by prior arrangement from Hampstead,
London. (Just off the A41, 2 miles from M1/A5/A41 BrentCross interchange).
Overseas shipping contact us first...
Purchasing Terms and Conditions
Terms and Conditions (Please read Before You Buy) if you can't agree on these terms please don't buy! |
|
Important Notice! Considering purchasing this item with a stolen credit card, then think again! We have been caught out only the once and now take precautions that would most certainly involve legal action being taken should you be found guilty of fraud. Don't waste your time or our's. |