http://blogs.msdn.com/b/andrewarnottms/archive/2008/08/05/if-the-ms-office-team-wrote-visual-studio.aspxSome humorous pros and cons to Visual Studio, if the Microsoft Office team were ever to take over. (disclaimer: this is a tongue in cheek post.&#160; No offense -- only laughs intended) Visual Studio 2008 would be able to load VC7 projects, modify themen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/andrewarnottms/archive/2008/08/05/if-the-ms-office-team-wrote-visual-studio.aspx#8834836Tue, 05 Aug 2008 23:09:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:8834836Robert 'Groby' Blum<p>Then maybe you guys need to start talking to the Office team. #1-#3 would be fairly nifty features that we certainly could use. #7 is a killer feature. </p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8834836" width="1" height="1">http://blogs.msdn.com/b/andrewarnottms/archive/2008/08/05/if-the-ms-office-team-wrote-visual-studio.aspx#8833923Tue, 05 Aug 2008 15:46:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:8833923int19h<p>11. Main menu and all toolbars would be replaced with a shiny new UI which would pretend that it's Vista even when run on Win2000; however, any modal dialogs that open afterwards would instead present the plain flat grey buttons even under Vista.</p> <p>12. You could embed a piece of VB.NET code inside a C# code file, and vice versa, and edit it in-place, with IntelliSense and other associated stuff switching dynamically as needed.</p> <p>13. The default font in the code editor would be Calibri.</p> <p>14. All methods created using class designer (or any other wizards) would have all parameters marked as &quot;ref&quot; by default.</p> <p>15. You could use SharePoint as source control for VS projects, and it would have a web part for server-side building.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8833923" width="1" height="1">