Talk:Visual Studio

Supported products

Each of the languages are themselves major products and thus have their own pages on wwikipedia, so I feel that most of this section is redundant. DominicConnor (talk) 18:58, 6 July 2011 (UTC)

vs2010 Codename

As a heads up, VS 2010 was not codenamed 'Rosario'. 'Rosario' referred to a Visual Studio Team System only release that was going to be based on VS 2008. This was going to be released separately from the lower SKUs, VS Pro, VS Express, etc. Rosario in this context also didn't refer to Rosario Strait, but rather to the Rosario resort on Orcas island. In the same way that the Rosario resort was built on Orcas island, VS 'Rosario' would be built on top of VS 2008 ('Orcas'). While the Team System Product Group were working on Rosario, the rest of the VS team were working on what was called 'Dev10'. It became clear as the product cycle continued they were going to be targeting a similar timeframe (end of 2009/start of 2010), and rather than ship a version of Rosario that was based on VS 2008, that it would be better to build it on top of VS 2010. Hence, the two products merged and were released together. —Preceding unsigned comment added by 131.107.0.81 (talk) 16:58, 1 July 2010 (UTC)

Do you have a source for any of the release being based on VS 2008 instead of 2010, and/or for Roasario and Dev10 having separate teams working on each? Ajm 80386 (talk) 13:28, 29 November 2023 (UTC)

Visual Studio 2010 for Windows Phone

i did not see a mention of the new addition to visual studio 2010. "visual studio 2010 for windows phone" is a new adittion for making phone applacations. —Preceding unsigned comment added by Keanwood (talk • contribs) 01:13, 15 April 2010 (UTC)

Its an after-release addon for download. It doesnt ship on the CD.94.168.168.153 (talk) 16:20, 21 May 2011 (UTC)

True. But that doesn't mean that it has no place in the article. Quite on the contrary, a good article must be broad in coverage. So, feel free to add something about it. Fleet Command (talk) 06:39, 22 May 2011 (UTC)

Survey

WP:Good article usage is a survey of the language and style of Wikipedia editors in articles being reviewed for Good article nomination. It will help make the experience of writing Good Articles as non-threatening and satisfying as possible if all the participating editors would take a moment to answer a few questions for us, in this section please. The survey will end on April 30.

• Would you like any additional feedback on the writing style in this article?

Sure, constructive feedback is always welcome. --soum ^talk 04:48, 21 April 2008 (UTC)

• If you write a lot outside of Wikipedia, what kind of writing do you do?

Mainly academic technical writing, aka, research papers. --soum ^talk 04:48, 21 April 2008 (UTC)

• Is your writing style influenced by any particular WikiProject or other group on Wikipedia?

Not anything particular. I just try to maintain a key things: short sentences, third person constructs, and not mixing active/passive voice. --soum ^talk 04:48, 21 April 2008 (UTC)

At any point during this review, let us know if we recommend any edits, including markup, punctuation and language, that you feel don't fit with your writing style. Thanks for your time. - Dan Dank55 (talk)(mistakes) 04:06, 21 April 2008 (UTC)

My GA Review of this article

A good article has the following attributes:

1. It is well written. In this respect:

(a) the prose is clear and the spelling and grammar are correct; and

(b) it complies with the manual of style guidelines for lead sections, layout, jargon, words to avoid, fiction, and list incorporation.

• I fixed some issues.
• Can you reword the paragraph about the Server Explorer tool—it is a little awkward.
• The Team Foundation Server paragraph has an incomplete sentence in the middle.
• Why the different font for names like "SVsSolution" and "SVsShell".
• Why are the languages available as part of the Express IDEs expressed in a list instead of prose?
• Pre-Installed Virtual Machines section has a string of bold text with no separating punctuation.
• Fix infobox (preview release? and languages (more?)) per Template:Infobox_Software

2. It is factually accurate and verifiable. In this respect, it:

(a) provides references to all sources of information, and at minimum contains a section dedicated to the attribution of those sources in accordance with the guide to layout;

(b) at minimum, provides in-line citations from reliable sources for direct quotations, statistics, published opinion, counter-intuitive or controversial statements that are challenged or likely to be challenged, and contentious material relating to living persons;[2] and

(c) contains no original research.

• Lot of citation issues. A lot of sections (as marked) need citations that support the text and inline citations.

3. It is broad in its coverage. In this respect, it:

(a) addresses the major aspects of the topic;[3] and

(b) stays focused on the topic without going into unnecessary details (see summary style).

• Are there any WikiArticle you could list in a See also section?
• The Supported products section seems to go into too much detail (and is also poorly sourced). Most of the current and previously supported products have their own WikiArticles, so not much need in dedicating an entire paragraph to each one--just provide a link. The article is pretty long, and (like I said) since this section is poorly sourced, I would cut it down significantly.

4. It is neutral; that is, it represents viewpoints fairly and without bias.

• Good

5. It is stable; that is, it is not the subject of an ongoing edit war or content dispute. Vandalism reversion, proposals to split or merge content, good faith improvements to the page (such as copy editing) and changes based on reviewers' suggestions do not apply. Nominations for articles that are unstable because of constructive editing should be placed on hold.

• No prior issues

6. It is illustrated, where possible, by images.[4] In this respect:

(a) images used are tagged with their copyright status, and fair use rationales are provided for non-free content; and

(b) the images are appropriate to the topic, and have suitable captions.[5]

• One image in good standing
• Not sure the Data tooltips screenshot is necessary.
• The Visual Studio Web Designer in code editor view image is no where close to the section that discusses the program. (The same could be said for most images--please think about placement.)

Conclusion

My initial feeling is to fail this GAN because I think it will take a while to fix all these issues, but since you've been waiting for a month to get this article reviewed, I'll be optimistic and put the article on hold for one week and give you a shot at it. Good luck! --Eustress (talk) 19:54, 15 May 2008 (UTC)

Thanks for taking the time to review this. I probably will not have enough time (or energy) to devote to this article anytime soon. But I will try to clarify some questions you raised:

• Why the different font for names like "SVsSolution" and "SVsShell"?

Because they are not just names but interfaces to plug some stuff into the Visual Studio infrastructure. For regular readers, it will suffice as name, but for informed programmers, it is <code>-ified to indicate that it has some special use.

• Why are the languages available as part of the Express IDEs expressed in a list instead of prose?

Because they are the same as the versions in "Included products". Duplicating the prose isn't necessary.

• Are there any WikiArticle you could list in a See also section?

I don't think there is much need. Relevant articles are already linked to in the prose.

• The Supported products section seems to go into too much detail (and is also poorly sourced).

Each paragraph provides a very high level overview only, and is only three or four lines in average. Chopping any further would make things lose context. There are many people who would not like to read an entire article for one language that is not in their core abilities. For this reason, a centralized and high level overview of supported products is necessary.

I realize sourcing is an issue and that facet needs to be improved. But won't have time anytime soon. Plus with the upcoming SP1, the article might get unstable. I suggest you fail it for now. --soum ^talk 20:16, 15 May 2008 (UTC)

Thanks for your understanding and for your responses to my inquiries. I'll fail it per our discussion, but feel free to let me know when it's up for GAN again—I'd be happy to review it if circumstances permit. Best --Eustress (talk) 21:12, 15 May 2008 (UTC)

Merge proposal

I propose the merge currently listed on this article. It appears that the creator of the article VSX was unaware of this article. Now I am no expert but both articles seem to be talking about the same things. I hence propose a merger of the article located at VSX to come here (and whatever info is already said here to just be deleted). As I said I am no expert, so maybe I have missed something, so anyone with knowledge about this topic should handle the move/next line of action. Cheers!Calaka (talk) 06:44, 28 May 2008 (UTC)

Conditional support. The extensibility section in this article is just an introduction. It can be covered more deeply, and for this reason the VSX article is of great potential. But the way it stands, its barely more than a personal essay and does not provide too much of an encyclopedic information not already here. If that is fixed and the VSX article fleshed out considerably, it should be linked from here as a {{main}} article. Failing that, it can be merged here. --soum ^talk 06:34, 29 May 2008 (UTC)

Oppose. Due to the length of the Visual Studio article, I think a full merge would be unnecessary, and would rather have VSX as a separate page going more in depth than a section here. — Northgrove 11:57, 17 September 2008 (UTC)

---

Visual Studio 2010

I skimmed the existing section on this product, and it seemed like it wasn't updated for the new (official) information here: http://msdn.microsoft.com/en-us/vstudio/products/cc948977.aspx. I'm just telling, because I don't have time for this myself at this exact moment. :-) Update: Also, more material here and here on Channel 9 as videos. — Northgrove 23:07, 30 September 2008 (UTC)

Should probably mention the supposed black box feature for reproducing test cases of bugs in applications which can be ticked on. Can't find the link at the moment, probably on MSDN but was mentioned on cnet news. —Preceding unsigned comment added by 24.162.101.108 (talk) 13:01, 10 October 2008 (UTC)

Also VS 2010 now has F# as standard, guess that ought to be there, in fact I can't find an article on F#, might start that. —Preceding unsigned comment added by DominicConnor (talk • contribs) 23:40, 8 February 2010 (UTC)

Parallelism support in VS 10

If someone is up for the task, here is the information you need: http://msdn.microsoft.com/en-us/magazine/cc817396.aspx. --soum ^talk 03:53, 3 October 2008 (UTC)

That's a framework addition, not a VS 10 addition. --Blowdart | ^talk 11:18, 22 October 2008 (UTC)

Not really. The APIs are framework addition, but the debugging and profiling tools are VS additions. --soum^talk 05:30, 24 April 2009 (UTC)

MS Babble?

This article is well written, however, some of the language is over precise and lacks a human element, things 'integrate' and have 'functionality', in the style of MS written material. Current MS IP (such as .NET) is discussed in detail although it has its own articles.

The article gives no context, no history. No mention is made of why Dev Studio was created, what inovations it has introduced, how it has influenced development practices. There is a version history but this is presented as a list of features.

So change it then. §FreeRangeFrog 23:33, 18 November 2008 (UTC)

I am surprised that this article mentions nothing about Visual Studio Premier Partner Edition... You can see Premier Partner Edition Setup and User Guide for more information... UU (talk) 15:11, 20 January 2009 (UTC)

It's because VSPPE is known as "Visual Studio Shell" since VS2008, and that is described in the article. -- int19h (talk) 20:32, 4 March 2009 (UTC)

source safe

Corrected wrong stuff, but now it's too long. Feel free to cut it back again. 150.101.166.15 (talk) 03:13, 26 November 2008 (UTC)

DreamSpark

It is unclear whether Dreamspark is just for US students or students worldwide. Can someone find out and add the necessary words in that sentence? Also, if you do, modify the DreamSpark article.

a_boardley (talk) 15:52, 27 November 2008 (UTC)

DreamSpark is available in many different countries. Just go to the website and check out the language selector dropdown... -- int19h (talk) 20:33, 4 March 2009 (UTC)

Im using it in the UK.81.23.50.232 (talk) 01:43, 16 January 2010 (UTC)

I wrote an article for the Register on it, and D is as international as MS can manage. —Preceding unsigned comment added by DominicConnor (talk • contribs) 23:41, 8 February 2010 (UTC)

Dont think its in india. You can get vouchers for Microsoft certification exams through DS and it says "Not available in india" and something about them not having valid student IDs. And seeing as you need a student ID to get onto DS.... 94.168.168.153 (talk) 16:22, 21 May 2011 (UTC)

Visual C# 2008

Hi, i'm refering to "The Visual C# 2008 compiler supports version 3.0 of the C# language specifications". If im not mistaken, version 3.5 is supported. Could somebody familiar with VS check this? Kind regards, -mafutrct (talk) 10:55, 10 December 2008 (UTC)

There's no such thing as "C# 3.5". You're probably confusing it with .NET 3.5. However, there is a version mismatch there - .NET 3.5 came with C# 3.0 (and .NET 3.0 was just a library add-on for .NET 2.0). -- int19h (talk) 20:34, 4 March 2009 (UTC)

Earlier Versions

The version history starts at 5.0 and should include earlier versions. I used 4.2, 4.1 and earlier versions (and was trying to find out their features). —Preceding unsigned comment added by 203.206.172.126 (talk) 01:58, 28 October 2009 (UTC)

Hello,

as a programmer having some experience with the classic Visual products, I'm currently working on a minor correction of the DE-WP Visual Studio article, regarding the version history. I'd like to inform you, that the mention of a "Visual Studio Version 4.0" is a mistake.

To my good knowledge as well as a result of research there actually was no Visual Studio version 4.0! While it's not only impossible to find any evidence for such a version, Microsoft clearly says "Visual Studio 97 is the first version of a suite of tools from Microsoft." (MSDN Library, TechEd 97 Conference Papers)

In "Visual Studio 97 is the first version of a suite of tools", the version reference must be (in other words, my interpretation is) to the tools, not Visual Studio. Sam Tomato (talk) 19:42, 17 March 2016 (UTC)

I guess there's some confusion with the version numbers of the language products (e.g. Visual C++ 4.2) and the integrated environment "Developer Studio".

Yes, Visual C++ was never an IDE. I had Microsoft C/C++ prior to Visual Studio. I believe that you are correct that the predecessor to Visual Studio was Developer's Studio. I still have the CD-ROMs and I have the first beta copy of the MSDN. I will check when I can. The history currently says "Prior to Visual Studio Version 4.0, there were Visual Basic 3, Visual C++, Visual FoxPro and Visual SourceSafe as separate products.". that is misleading, none of those were IDEs. I will correct that when I have verified my memory from actual Microsoft information. Sam Tomato (talk) 19:42, 17 March 2016 (UTC)

Ed 79.224.218.207 (talk) 14:51, 16 December 2012 (UTC)

Visual Studio 97 was not "Microsoft's first attempt at using the same development environment for multiple languages". The predecessor to Visual Studio was. Sam Tomato (talk) 19:42, 17 March 2016 (UTC)

Microsoft Visual Studio 1998 bis 2003

Version 6.0

Das Microsoft Visual Studio 6.0 wurde von Microsoft entwickelt fuer die Betriebssysteme der Jahre 1998 bis 2000 Windows 98, Windows NT, Windows ME, Windows 2000.

Das 1998 veröffentlichte Microsoft Visual Studio 6.0 war eine Sammlung der Programmiersprachen Visual Basic 6.0, Visual C++ 6.0, Visual J++ und den Programmiersprachenanwendungen Visual InterDev (ASP Webapplikationsentwicklung), Visual FoxPro.

„Visual J++“ wurde nach dieser Version (aber in der teuersten Version Microsoft Visual Studio 6.0 Enterprise III/1999 noch in Deutschland verkauft) eingestellt. Sun hatte die Weiterentwicklung verboten. Visual FoxPro wurde nach dieser Version getrennt weiterentwickelt und ist nicht mehr Bestandteil von Visual Studio nach der Version 6, da die wenigsten Visual-Studio-Kunden auch Visual-FoxPro-Programmierer sind.

Neben der Programmierumgebung selbst sind noch diverse Tools zur Unterstützung des Entwicklers bzw. zur Erweiterung von Team-Arbeits-Funktionen integriert. Einige wichtige Module sind die MSDN-Library als eingebundene kontextsensitive Online-Hilfe, „DDE Spy“, „Spy++“ und der Verpackungs- und Weitergabe-Assistent.

Durch das integrierte Microsoft Visual SourceSafe ist es mehreren Personen möglich, gleichzeitig an zentralen Projekten zu arbeiten. Visual SourceSafe erledigt Aufgaben wie Versionsmanagement, Dateisperren und dergleichen. Es gibt allerdings zahlreiche Visual-Studio-AddIns anderer Anbieter, mit denen alternative Versionskontrollsysteme wie Subversion oder CVS auf ähnlich einfache Weise verwendet werden können.

Durch Verwendung der ActiveX-Technik ist die Entwicklungsumgebung als solche erweiterbar, die hierfür notwendigen Module werden als AddIns bezeichnet.

In der Microsoft Visual Studio 6.0 Enterprise Version war die MSDN Textbibliothek und Codebibliothek auf 2 CDs beigelegt. Die Entwicklungsumgebung zusammen mit den Programmiersprachen umfasste 4 CDs und die fuenfte CD war die fuer die Programmiersprache Visual J++.

http://de.wiki.x.io/w/index.php?title=Microsoft_Visual_Studio&action=edit&section=4

Microsoft Visual Studio 6.0 (Enterprise edition)

The next version, version 6.0, was released in June 1998 and is the last version to run on the Windows 9x platform. The version numbers of all of its constituent parts also moved to 6.0, including Visual J++ which jumped from 1.1, and Visual InterDev which was at 1.0. This version was the basis of Microsoft's development system for the next four years, as Microsoft transitioned their development focus to the .NET Framework.

Visual Studio 6.0 was the last version to include the COM-based version of Visual Basic; subsequent versions would include the version of the language based on .NET. It was also the last version to include Visual J++, which was removed as part of a settlement with Sun Microsystems that required Microsoft to stop producing programming tools that targeted the Java Virtual Machine.

Visual Basic, Visual C++, and Visual FoxPro had separate IDEs, while Visual J++ and Visual InterDev shared a common new environment. This new IDE was designed with extensibility in mind, and would go on (after several internal revisions) to become the common environment for all languages with the release of Visual Studio .NET. Visual Studio 6.0 was also the last version to include Visual FoxPro.

As usual, Visual Studio 6.0 came in several editions: Standard, Professional & Enterprise. The Enterprise edition contains extra features not found in Standard or Professional edition, which includes:

• Application Performance Explorer
• Automation Manager
• Microsoft Visual Modeler
• RemAuto Connection Manager
• Visual Studio Analyzer

http://en.wiki.x.io/w/index.php?title=Microsoft_Visual_Studio&action=edit&section=14 82.109.84.114 (talk) 17:05, 6 January 2010 (UTC)

Microsoft Macro Assembler

I have been working in the Microsoft Macro Assembler page and it is starting to have some reliable content. It has been a component of the Visual Studio development environment since the processor pack dated 2000 and should be added to this page. I have not edited the current page as there are considerations in terms of its content and layout that I am not familiar with.

Hutch48 (talk) 11:44, 14 January 2010 (UTC)

Helpful reference information for users

As the history of this page evidences, people are interested in more than basic product information when reading articles like this. Maybe a good way to provide that information, without compromising Wikipedia policy, is to add links to sites like [MSDN] and [StackOverflow] at the bottom of the article? LarsKemmann (talk) 15:22, 1 February 2010 (UTC)

I agree. I also think it needs a table of versions numbers. It is confusing enough that VS2010 is version 10 (from which a lot of people extrapolate that VS2008 was version 8). However, the confusion with the file version numbers had me pulling my hair out (since VS2003 the file format version numbers have been one more than the product version number!?!@#$!). —Preceding unsigned comment added by 203.41.222.1 (talk) 01:15, 17 September 2010 (UTC)

Cool Section

• This IT page needs many inputs.

First of all, it should compare various versions of the tool and show main features in a table for the programmers to review.

122.169.93.238 (talk) 07:31, 12 February 2010 (UTC)

Do you mean comparing different versions (e.g., VS6, VS2002 ".NET", VS2008, VS2010...) or different editions (e.g., Express, Professional, Ultimate...)? The former is currently handled by the different sections which talk about the product, and since that kind of comparison is mostly for historical interest, it makes sense to write it in prose. The latter is already in the article. What is the value of comparing different versions' features over time in a table? Maybe a small summary table would be helpful? --LarsKemmann (talk) 15:35, 12 February 2010 (UTC)

C# in "Written in" field

Someone recently removed C# from the written in field. Due to the code editor using WPF now and the lack of external XAML files, according to information on MSDN it is impossible for them not to be using at least some C#, if only in the AssemblyInfo.cs of a resource-holding DLL. Washington Irving Esquire (talk) 11:47, 20 October 2010 (UTC)

That looks like Original Research to me; even less than that. Such contents are not allowed in Wikipedia. In Wikipedia, everything must come from a reliable source. Complex and controversial conclusions like this are not allowed, especially given the fact that you have assumed too much for granted. Fleet Command (talk) 17:37, 20 October 2010 (UTC)

I don't think my statement required any assumption as the MSDN page makes it clear that a C# DLL is necessary to implement WPF in C++. I'm not going to argue about it though, I'm not the one that originally added C# to that field and so I don't really care either way, was just stating a thought. Washington Irving Esquire (talk) 18:07, 20 October 2010 (UTC)

VS 2010, Visual Studio Shell, partner edition

Is there a 2010 version of "Visual Studio Shell" (2008) aka "Visual Studio Premier Partner Edition" (2005)? I haven't found anything, so I'm thinking they may have dropped this. —Preceding unsigned comment added by 203.206.162.148 (talk) 05:31, 10 November 2010 (UTC)

There is one. See:

http://msdn.microsoft.com/en-us/library/bb129445%28v=VS.100%29.aspx

Fleet Command (talk) 06:29, 10 November 2010 (UTC)

Web-browsing

I know that some things in Microsoft Visual Studio use other objects from Windows.

The web browser uses Internet Explorer to run Internet (Microsoft Web Browser uses a type of Internet that does not use the computer theme unless its Windows Classic. The web browser is used in all of the Visual Studio tools. — Preceding unsigned comment added by WiiRocks566 (talk • contribs) 21:02, 18 July 2011 (UTC)

Visual Studio Express is Trialware, not Freeware

This needs to be separately verified: Visual Studio 2010 Express has a 30 day trial period for the product. I'm not sure what the status of earlier versions of Visual Studio Express is. — Preceding unsigned comment added by 129.89.251.67 (talk) 20:20, 10 August 2012 (UTC)

Visual Studio Team System part

The part about Visual Studio Team System is quite messed up and confusing according to what information is possible to get from MS pages. First - Team System is not an edition itself (although put like that in the article), which is not emphasised. Secondly, Team System offers 4 self-standing editions, one suite and a server product (VS Team Suite, VS Team Foundation Server (TFS), VS Team Edition for Software Architects, VS Team Edition for Software Developers, VS Team Edition for Database Professionals, VS Team Edition for Software Testers). VS Team Suite is a bundle of three products itself (VS Team Architect Edition, VS Team Developer Edition and VS Team Test Edition). The names of products in this section of article are inaccurate and might be misleading. Athae (talk) 11:31, 6 September 2011 (UTC)

Visual Studio 11 doesn't produce XP-compatible executables

Programs built with Visual Studio 11 don't run on Windows XP. This is because the C runtime library hard-links to the FlsAlloc series of functions and GetTickCount64.

It'd be nice to mention that 2010 is the last version to support targeting XP, but it's original research of mine. -- Myria (talk) 05:34, 21 September 2011 (UTC)

Disagree. How do you know it is not a bug that will be fixed in production release? Besides, you should realize this is not how Wikipedia works. You require a reliable source to say such thing in the article. For more information, see Wikipedia:Verifiability. Fleet Command (talk) 11:09, 23 September 2011 (UTC)

The code in the C runtime library in 8.0-10.0 that automatically detected and used FlsAlloc if present was removed in 11.0, instead hard-linking to FlsAlloc. It looks very intentional. I posted it here instead of just editing the article in the hopes that someone would know a reliable source that has this information. Myria (talk) 21:34, 24 September 2011 (UTC)

This is the closest I've found to a Microsoft acknowledgement that programs built with Visual Studio 11 won't run on Windows XP: http://connect.microsoft.com/VisualStudio/feedback/details/690617/bug-apps-created-with-crt-and-mfc-vnext-11-cannot-be-used-on-windows-xp-sp3 — Preceding unsigned comment added by Myria (talk • contribs) 21:14, 26 September 2011 (UTC)

Looks like the issue only applies to Microsoft Foundation Class Library, not the whole C++ language. (Oh, good, I never use MFC.) But your source is good enough, since it is a Microsoft spokesperson who said that. You may add it to the article. However, situation might quickly change. Be sure to add that it is only the case in pre-beta stage. Fleet Command (talk) 10:08, 27 September 2011 (UTC)

It looks like that only applies to MFC/CRT. I would imagine that managed apps written in C# and VB.NET continue to work even on Win XP. A Quest For Knowledge (talk) 10:29, 27 September 2011 (UTC)

Correct. And this is just the case with pre-beta (developers preview) stage. Fleet Command (talk) 09:43, 28 September 2011 (UTC)

Visual Studio 2012

Visual Studio is being refereed to as Visual Studio 2011 and Visual Studio 2012. This should be fixed to so that they all say 2012. Microsoft's website refers to it only as Visual Studio 2012. --Jimv1983 (talk) 19:59, 7 June 2012 (UTC)

Visual Studio 2012 edits

In this sentence: Visual Studio 2012 Beta was released on February 1, 2012 and can be downloaded from the product's home page.

The release date was February 29, 2012 (at the time, the product name was Visual Studio 11 Beta) and the product's current home page is http://www.microsoft.com/visualstudio/11 (ref: Visual Studio 11 Beta Announcement). The old link was for Visual Studio 11 Developer Preview, which released at BUILD on September 14, 2011 (ref: Visual Studio 11 Developer Preview Announcement) to MSDN Subscribers, and then two days later to the general public.

Rob (talk) 21:47, 28 July 2012 (UTC)

Not done: With 4 days and 10 edits you should be able to correct it. You could also ask at help desk. I am just clearing the backlog of requests.--Canoe1967 (talk) 10:04, 1 August 2012 (UTC)

Visual studio 2012 is already available for download

You should correct the release date for VS2012 and add it to the table. The reference for this is: http://blogs.msdn.com/b/somasegar/archive/2012/08/15/visual-studio-2012-and-net-4-5-now-available.aspx. You can download VS2012 and .net4.5 from http://www.microsoft.com/visualstudio/11/en-us/downloads#vs. — Preceding unsigned comment added by 83.241.139.34 (talk) 09:14, 16 August 2012 (UTC) Why has no one updated the article? — Preceding unsigned comment added by Maciekpak (talk • contribs) 15:45, 26 August 2012 (UTC)

VS 2012 screenshot

Since VS2012 is practically out, the screenshot at the top of article needs to be from it, instead of 2010 (so at least it would be compatible with the 2012 that already appears over there) — Preceding unsigned comment added by 84.108.130.94 (talk) 11:13, 17 August 2012 (UTC)

VS 12 different Editions

the table is out-dated, it should be updated according to this http://www.microsoft.com/visualstudio/11/en-us/products/compare 175.143.250.227 (talk) 15:14, 24 August 2012 (UTC)

latest preview version : Visual studio 2013

http://msdn.microsoft.com/en-US/windows/apps/bg182409 http://www.microsoft.com/visualstudio/eng/2013-downloads — Preceding unsigned comment added by 41.42.164.165 (talk) 17:06, 26 June 2013 (UTC)

Thanks, I've updated the release information.  drewmunn  talk  18:10, 26 June 2013 (UTC)

C99 standard

Article seems to lack which standards that are supported. This is essential atleast for the C-laguage. Do any of the more recent versions support the C99 standard (including the new type of dynamical memory allocation). 83.249.160.230 (talk) 23:47, 2 September 2013 (UTC)

The picture of VS2013 Enterprise edition

I don't know there is an "Enterprise" edition for Visual studio 2013... There's "professional", "premium","ultimate"... Lbobrov (talk) 21:04, 10 January 2014 (UTC)

Hi. Thanks for the tip. I checked. You seem to be right. I put the file up for speedy deletion per WP:CSD#F4. Best regards, Codename Lisa (talk) 00:37, 11 January 2014 (UTC)

Visual Studio "14" links

• http://blogs.msdn.com/b/visualstudioalm/archive/2014/06/04/visual-studio-14-ctp-now-available-in-the-virtual-machine-azure-gallery.aspx (CTP now available)

• http://blogs.msdn.com/b/vcblog/archive/2014/06/18/crt-features-fixes-and-breaking-changes-in-visual-studio-14-ctp1.aspx (run-time library changes)

Built-in languages

The preamble states that C is a built-in language. I don't think that this is correct. Support for a C-library (C99) does not mean that the C-language can be compiled or is supported in other ways. It only means that other languages can use functions provided by this library. --O. Jacot-Descombes (talk) 19:30, 10 September 2014 (UTC)

Here is an MSDN page describing how to compile C programs using Visual Studio tools. There is also the C Language Reference on the same site. Seems like C is supported. --Mark viking (talk) 19:38, 10 September 2014 (UTC)

What about that '95 version in the history table?

Hey guys,

the discussion (/talk) page of the German article states since now three years (!) a seeming proof that there was no Visual Studio 95 or "Visual Studio" with internal 4.0 number.

A user there (Ed) quotes Microsoft: "Visual Studio 97 is the first version of a suite of tools from Microsoft."

IF YOU CAN NOT PROVE THE EXISTENCE OF VISUAL STUDIO 4.0 PLEASE CONSIDER TAKING IT OFF THE LIST. Not screaming.

Thanks. -- Enrico — Preceding unsigned comment added by 91.32.83.208 (talk) 14:29, 14 July 2015 (UTC)

Microsoft Visual Studio Community Edition

I tried installing this program but stopped at the point where it requires registration. It cannot be used without registering.

Here's the relevant section of the license agreement:

DATA. The software may prompt you from time to time to obtain a license key, such as by signing into a Microsoft account. If you do not obtain and enter a new license key when prompted, you may not be able to use the software and access your data in the software. The software may collect information about you and your use of the software, and send that to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may opt-out of many of these scenarios, but not all, as described in the product documentation. 

The term "Community Edition" is misleading - it's really a full trial edition for 30 days, and then a restricted edition. It's bait and switch marketing. It would be good if the article mentioned this.

Mtj (talk) 18:14, 28 February 2016 (UTC)

Hello, Mtj

The article already mentions that the app is registerware. (See infobox.) The problem starts with the third paragraph of your message above: You need a source that clearly says after 30 days, which features are unavailable.

Best regards,

Codename Lisa (talk) 19:11, 28 February 2016 (UTC)

You do realize that it's trial ware, don't you? That's what the 'from time to time" in the EULA means. Microsoft are being silent on what features are lost after 30 days. Why put the burden on us to do research so as to name the lost features? I think the infobox needs to be edited to say that it is both register ware and trial ware.

Mtj (talk) 21:14, 29 February 2016 (UTC)

Here is our policy before you try anything rash: A source is required. Original research is forbidden. Personal interpretation of the source to advance a positions not explicitly mentioned in the source, is also forbidden.

Also, it is "trialware" not "trail ware"! And "Microsoft" is singular, not plural.

—Codename Lisa (talk) 22:10, 29 February 2016 (UTC)

Let's address the trial ware issue first, and leave the article to later. Do you agree that it is trial ware or don't you? Have you tried downloading it, and seen the registration screen?

Mtj (talk) 22:43, 29 February 2016 (UTC)

I've been using it throughout February to complete a "Know It! Prove It!" course that Microsoft is hosting. I haven't noticed a feature decline yet.

When I installed it, I noticed I have 30 days to activate the product before it stops working. I did so. The activation was free of charge.

Best regards,

Codename Lisa (talk) 07:48, 1 March 2016 (UTC)

Good. Now we're talking. I couldn't get it going without accepting the trial offer. I suspect that you just accepted the trial offer without looking too closely at it, since you intended to install it anyway. I didn't want to proceed without knowing what was on trial and what wasn't, so I declined the offer. Which means I can't use it. So, as far as I'm concerned, it's trial ware.

Mtj (talk) 12:53, 1 March 2016 (UTC)

You suspect wrong. Installing Visual Studio was part of the training. I was forced to look closely. Plus, I usually pay much attention to details.

There is no trial offer. There is a 30-days timer for getting a license; only for Community edition this license is free. That's what we call "Registerware". Are you sure you have downloaded the Community edition?

Best regards,

Codename Lisa (talk) 15:29, 1 March 2016 (UTC)

Yes - I did choose the community edition. It offered me features, and I chose them, then it downloaded them, then it came up with the license agreement. Perhaps I was choosing features that aren't included in the community edition, so it offered me a trial license instead of a registration.

Are you saying that you were able to get it going without having to agree to anything up front? Not even register it? — Preceding unsigned comment added by Mtj (talk • contribs) 16:41, 1 March 2016 (UTC)

Requesting update to Application Lifecycle Management

Hello, my name is Doug Erickson and I am an employee of Microsoft working the Cloud+Enterprise division. I am currently correcting and cleaning up topics related to Microsoft Visual Studio Team Services and our ALM products to better represent the current state and features of the products. Please review the changes below and let me know if they are acceptable to you, and thank you for your consideration!

I would like to edit the "Application Lifecycle Management" section to the text below.

Visual Studio Application Lifecycle Management (Visual Studio ALM) is an integrated collection of software development tools developed by Microsoft. These tools consist of client (Visual Studio 2015 Community and greater editions), server (Team Foundation Server), cloud services (Visual Studio Team Services) and other products. Visual Studio ALM supports team-based development and collaboration, project management, DevOps, packaging, continuous integration, and continuous delivery for apps and services.

Between 2005 and 2008, the brand was known as Microsoft Visual Studio Team System (VSTS). In October 2009, the Team System brand was renamed Microsoft Visual Studio ALM with the Visual Studio 2010 (codenamed 'Rosario') release. . Visual Studio Team Services debuted as Visual Studio Online in 2013 and was renamed in 2015.

References

DougE MSFT (talk) 05:59, 5 March 2016 (UTC)

Not done

Hello, Doug

Before I start, thank you for coming here. I must say it is good to see that Microsoft employees are starting to take COI seriously. Still, the template you should have used is {{Edit request}}, not {{Edit-request}}. If you had previewed your message, you'd have seen it.

Now, I am afraid your suggested contribution has the following problems, four of them are blocking issues:

• "In Visual Studio 2005 and Visual Studio 2008 the brand was known" was changed into "Between 2005 and 2008, the brand was known as". This is only and only correct if Microsoft has later issued an update for VS2005 and VS2008 to eliminate the name (as it did to Windows Essentials and Microsoft Office to eliminate "SkyDrive") and the general public has chiefly stopped using the term. Both needs a supporting source.
• You have not explained why you removed this sentence: "These tools include IDEs, source control, work items, collaboration, metrics, and reporting tools." We cannot remove content without an edit summary.
• "VSALM" does not appear in your source. We cannot accept inventive acronyms. "ALM" appears in the old source.
• "other products" is a weasel word. What other products? Either name them or never even imply that there are others.

Non-blocking issues:

• You have placed <ref>...</ref> before punctuation. Wikipedia MOS requires them to be after punctuation.

Best regards,

Codename Lisa (talk) 17:21, 5 March 2016 (UTC)

Thank you for the specific and targeted feedback! I'm a newbie here and I appreciate the clear responses. I have made an update and (I hope) have addressed my mistakes.

Here is my edit summary:

1. Changed "These tools include IDEs, source control, work items, collaboration, metrics, and reporting tools" to "These tools currently consist of the IDE (Visual Studio 2015 Community and greater editions), a server product (Team Foundation Server), and cloud services (Visual Studio Team Services)" to clarify the three major products for delivery of the ALM tools. Added a citation from ArsTechnica.
2. Added "VSALM 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." to break out the list of scenarios covered across the VSALM collection of tools, as well as to reflect what is currently on the cited MSDN page. Moved the earlier MSDN citation here for clarity.

Hearing your counsel, I reverted your other concerns, such as the "between 2005 and 2008" change. I am also reverting back to "VSALM" although that is not an acronym we formally use in marketing, as I acknowledge that it may have prevalence in the community that I am not aware of, and thus should let the community decide.

Visual Studio Application Lifecycle Management (VSALM) 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).

VSALM 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.

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 Microsoft Visual Studio ALM with the Visual Studio 2010 (codenamed 'Rosario') release.

Visual Studio Team Services debuted as Visual Studio Online in 2013 and was renamed in 2015.

References

DougE MSFT (talk) 22:54, 7 March 2016 (UTC)

 Doing... Codename Lisa (talk) 23:02, 7 March 2016 (UTC)

 Done

Hello, Doug

I have implemented your request with a few changes:

• VSALM is removed. As I told you, it does not appear in the source! (Of course, your original request didn't have VSALM; it only lacked the old source that said "ALM"!) In this revision, you retained the old source but also reverted to VSALM.
• Ars Technica citation corrected. You had by mistake added "Ars Technica" in |publisher= parameter while it should go into |work=. The publisher is Condé Nast.
• |work= parameter was added to Brian Harry's and Octavie van Haaften's blogs.
• Two of the paragraphs were appended to their predecessor because of their contextual similarity.

Best regards,

Codename Lisa (talk) 23:43, 7 March 2016 (UTC)

SQL Server

I am having difficulty determining what version of SQL Server is installed with Visual Studio 2015 Community Version. It would help if that information was provided for each version of Visual Studio. SQL Server is mentioned a few times relevant to what is supported but there is nothing about what is included. Sam Tomato (talk) 19:25, 17 March 2016 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on Microsoft Visual Studio. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Corrected formatting/usage for http://www.onedotnetway.com/writing-visual-studio-2010-shell-in-wpf-reflects-confidence

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

N An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked= to true

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 06:00, 2 April 2016 (UTC)

"15" Preview 4

I have updated the main text for the latest release Preview 4.

But it is not obvious how to fix the page template, currently stuck on Preview 3.

I'd welcome helpful suggestions.

NoPolymath (talk) 22:23, 22 August 2016 (UTC)

@NoPolymath: Hi. :) You should click on the [±] link. You'll be taken to the page where the information is located. Consider studying Template:Infobox software for more information. Best regards, Codename Lisa (talk) 06:27, 24 August 2016 (UTC)

Requesting edits to the Introduction section for Microsoft Visual Studio

Hi my name is Billy Learned and I would like to submit an addition to this page for the Introduction section directly above the Architecture section for Microsoft Visual Studio.

Thank you very much!

Microsoft Visual Studio product family is a collection of developer-focused tools, services, and subscription programs from Microsoft. It is made up of an integrated development environment (IDE), code editor, and software as a service (SaaS) based offerings to support developing, testing, building, and deploying software applications across the Android, Linux, iOS, Mac and Windows operating systems. Some of the tools and services offered in this collection are the Visual Studio IDE (for PC), Visual Studio for Mac (IDE), Visual Studio Code, Visual Studio Team Services, and Visual Studio Mobile Center. Developers can gain access through the free Visual Studio Dev Essentials program and/or via the paid Visual Studio Subscriptions.

The Visual Studio IDE is an integrated development environment (IDE) from Microsoft. It is used to develop computer programs for Microsoft Windows, as well as web sites, web applications and web services. 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.

The Visual Studio IDE 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 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 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).

The Visual Studio IDE supports 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, C++ and C++/CLI (via Visual C++), VB.NET (via Visual Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2010). Support for other languages such as Python,). Support for other languages such as Python, Ruby, Node.js, and M among others is available via language services installed separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Java (and J#) were supported in the past.

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

Bdlearned (talk) 03:57, 31 January 2017 (UTC)

References

Not done:. This contribution is an attempt to hijack the topic. This article is about Visual Studio the IDE. You are attempt to hijack it for a the topic of Visual Studio the brand name, which you call "product family". The problem is Visual Studio the IDE is a notable topic. Visual Studio the brand name is not. Even if it were notable, anyone in Wikipedia is still allowed to write an article on a notable topic (like Visual Studio the IDE) and nobody is allowed to hijack that topic.

Co-branding is an advertisement tactic and while we might covert it in the article for the sake of accuracy (we have a small section on Visual Studio Code and other VS-branded apps) Wikipedia is not a Microsoft division and is not obliged to change its perspective whenever Microsoft saw fit to do for making more money, acceptance, etc.

Best regards,
Codename Lisa (talk) 07:12, 31 January 2017 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 3 external links on Microsoft Visual Studio. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://archive.is/20120530/http://www.lextrait.com/Vincent/implementations.html to http://www.lextrait.com/Vincent/implementations.html
• Corrected formatting/usage for https://msdn.microsoft.com/magazine/mt790181
• Corrected formatting/usage for https://msdn.microsoft.com/magazine/mt790181

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 14:04, 29 April 2017 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 2 external links on Microsoft Visual Studio. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20090815083038/http://www.microsoft.com/presspass/press/2008/sep08/09-29VS10PR.mspx to http://www.microsoft.com/presspass/press/2008/sep08/09-29VS10PR.mspx
• Added archive https://web.archive.org/web/20090815083038/http://www.microsoft.com/presspass/press/2008/sep08/09-29VS10PR.mspx to http://www.microsoft.com/presspass/press/2008/sep08/09-29vs10pr.mspx

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 19:40, 10 June 2017 (UTC)

What is "Git Control"?

Sub section Visual Studio Code: What is the meaning of "Git Control"? Should it just be "Git source control"? --Mortense (talk) 17:15, 3 June 2018 (UTC)

TODO - Hardware/Software Requirement summary table

I think it would be useful adding a table with the software and hardware requirement for each version (minimal and recommanded). Manta Ray DeeJay (talk) 16:31, 14 November 2019 (UTC)

".csproj" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect .csproj. Please participate in the redirect discussion if you wish to do so. 1234qwer1234qwer4 (talk) 19:48, 6 April 2020 (UTC)

Does MS stop all feature/bug updates when it releases a new version of VS? (because it seems that way)

It's always seemed to me whatever bugs exist in VS X are deemed "won't fix" the day after VS "Y" is published. I mean does it do any good to report bugs on past versions of VS? I would like a section with a heading on the release philosophy and rationale for leaving features unfinished (e.g. C++ standards that are partially implemented) forever instead of back-porting simple fixes/omissions, or is this just my imagination? --184.20.10.253 (talk) 20:19, 10 November 2020 (UTC)

For bugfix, no, because at least VS 2017 still have some tooling version updates and bug fix, one is even released when you started this topic. New features definitely don't get backported to the older version, and if you consider the C++ standards support as unfinished, then it definitely never going to be finished any time soon. However, the lack of backporting is rather irrelevant for most users, open-source and indie dev can just easily get the latest version, while corporates are expected to just renew the subscriptions that give them access to all supported versions. I don't see much discussion on the lack of backporting on other mainstream software, it's either expected and exist, or it doesn't and people don't fuss about it.Martheencp (talk) 10:20, 4 December 2020 (UTC)

Community Editions vs. Express Editions

First contribution to Wikipedia. I've used, as a hobbyist programmer, Visual Studio for several years, and I believe that all the Express editions are no longer supported, and the only reference to them is this article should be historical in nature. I use the Community editions and am sure the following statements are true: 1. They are free for many/most users. 2. They are fully featured editions. 3. They are NOT trial products. 4. Many (perhaps all) year-labeled editions can be installed side-by-side. — Preceding unsigned comment added by Geezzeer (talk • contribs) 19:06, 15 April 2022 (UTC)

Page name: I noticed that the Japanese page says: Microsoft Visual Studio, but the English title says: Visual Studio

Hello, I am an infrequent contributor to Wiki, but a regular reader. As the section title says... Honestly, it seems like the Japanese title is more accurate, especially from search engines. Thoughts? Kevinarpe (talk) 16:25, 5 January 2024 (UTC)

source code editor

This article mentions that Visual Studio has a source-code editor. Does that source code editor have a name? Is that source code editor perhaps Visual Studio Code, or is it some other editor? --DavidCary (talk) 17:10, 18 November 2024 (UTC)

Visual Studio Code is a separate, standalone piece of software. I don't think the editor in Visual Studio has a special name. –CWenger (^ • @) 21:26, 18 November 2024 (UTC)

Are there any reliable sources that explicitly say the two editors are independent? This article does a pretty good job naming the various parts and pieces of Visual Studio -- Cider, Windows Forms Designer, Visual Studio Shell , etc. -- so I will be very surprised if it turns out that its editor has no name. --DavidCary (talk) 21:50, 18 November 2024 (UTC)

Not sure about a source but you can see here they are distinct pieces of software. –CWenger (^ • @) 22:17, 18 November 2024 (UTC)

extensibility

This article mentions that Visual Studio has some sort of extensibility ( Visual Studio#Extensibility ). Does the extensibility approach have a name? Does it perhaps use VSX ("Visual Studio Extensibility") or MEF ("Managed Extensibility Framework") or some other extensibility approach? --DavidCary (talk) 21:50, 18 November 2024 (UTC)