Talk:Visual Studio

message: 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)
thread_title: Supported products

message: 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)
replies: text: 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)
thread_title:  vs2010 Codename 

message: 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)
replies: text: Its an after-release addon for download. It doesnt ship on the CD.94.168.168.153 (talk) 16:20, 21 May 2011 (UTC)
replies: text: 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)
thread_title:  Visual Studio 2010 for Windows Phone 

message: 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)
replies: text: Mainly academic technical writing, aka, research papers. --soum talk 04:48, 21 April 2008 (UTC)
replies: text: 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)
thread_title:  Survey 

message: 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)
replies: text: 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  article. Failing that, it can be merged here. --soum talk 06:34, 29 May 2008 (UTC)

text: 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)
thread_title: Merge proposal

message: 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)
thread_title:  Visual Studio 2010 

message: 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)
replies: text: That's a framework addition, not a VS 10 addition. --Blowdart | talk 11:18, 22 October 2008 (UTC)
replies: text: Not really. The APIs are framework addition, but the debugging and profiling tools are VS additions. --soumtalk 05:30, 24 April 2009 (UTC)
thread_title:  Parallelism support in VS 10 

message: 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)
replies: text: 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)
thread_title:  MS Babble? 

message: 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)
thread_title:  source safe 

message: 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)
replies: text: 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)
thread_title:  DreamSpark 

message: 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)
replies: text: 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)
thread_title:  Visual C# 2008 

message: 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)
replies: text: 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)

text: 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)
thread_title:  Earlier Versions 

message: === 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.wikipedia.org/w/index.php?title=Microsoft_Visual_Studio&action=edit§ion=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.wikipedia.org/w/index.php?title=Microsoft_Visual_Studio&action=edit§ion=14
82.109.84.114 (talk) 17:05, 6 January 2010 (UTC)
thread_title: Microsoft Visual Studio 1998 bis 2003

message: 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.wikipedia.org/w/index.php?title=Microsoft_Visual_Studio&action=edit§ion=14
82.109.84.114 (talk) 17:05, 6 January 2010 (UTC)
thread_title: Microsoft Visual Studio 6.0 (Enterprise edition)

message: 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)
thread_title: Microsoft Macro Assembler

message: 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)
thread_title:  Helpful reference information for users 

message: * 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)
replies: text: 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)
thread_title:  Cool Section 

message: 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)
replies: text: 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)
replies: text: 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)
thread_title:  C# in "Written in" field 

message: 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)
replies: text: There is one. See:http://msdn.microsoft.com/en-us/library/bb129445%28v=VS.100%29.aspxFleet Command (talk) 06:29, 10 November 2010 (UTC)
thread_title:  VS 2010, Visual Studio Shell, partner edition 

message: 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)
thread_title:  Web-browsing 

message: 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)
thread_title:  Visual Studio Express is Trialware, not Freeware 

message: 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)
thread_title:  Visual Studio Team System part 

message: 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)
replies: text: 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)
replies: text: 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)

text: 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)
replies: text: 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)
replies: text: 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)
replies: text: Correct. And this is just the case with pre-beta (developers preview) stage. Fleet Command (talk) 09:43, 28 September 2011 (UTC)
thread_title:  Visual Studio 11 doesn't produce XP-compatible executables 

message: 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)
thread_title:  Visual Studio 2012 

message: 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)
replies: text: 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)
thread_title:  Visual Studio 2012 edits 

message: 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)
thread_title:  Visual studio 2012 is already available for download 

message: 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)
thread_title:  VS 2012 screenshot 

message: 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)
thread_title:  VS 12 different Editions 

message: 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)
replies: text: Thanks, I've updated the release information.  drewmunn  talk  18:10, 26 June 2013 (UTC)
thread_title:  latest preview version : Visual studio 2013 

message: 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)
thread_title:  C99 standard 

message: 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)
replies: text: 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)
thread_title:  The picture of VS2013 Enterprise edition 

message: 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)
replies: text: 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)
thread_title:  Built-in languages 

message: 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)
thread_title:  What about that '95 version in the history table? 

message: 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)
thread_title:  SQL Server 

message: Hello fellow Wikipedians,
I have just modified  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 ).
Cheers.—cyberbot IITalk to my owner:Online 06:00, 2 April 2016 (UTC)
thread_title:  External links modified 

message: 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)
replies: text: 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)
thread_title:  "15" Preview 4 

message: 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.
Cheers.—InternetArchiveBot (Report bug) 14:04, 29 April 2017 (UTC)
thread_title:  External links modified 

message: 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.
Cheers.—InternetArchiveBot (Report bug) 19:40, 10 June 2017 (UTC)
thread_title:  External links modified 

message: 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)
thread_title:  What is "Git Control"? 

message: 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)
thread_title:  TODO - Hardware/Software Requirement summary table 

message: 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)
thread_title:  ".csproj" listed at [[Wikipedia:Redirects for discussion|Redirects for discussion]] 

message: 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)
thread_title:  Does MS stop all feature/bug updates when it releases a new version of VS? (because it seems that way) 

message: 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)
thread_title:  Community Editions vs. Express Editions 

message: 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)
thread_title:  Page name: I noticed that the Japanese page says: Microsoft Visual Studio, but the English title says: Visual Studio