Visual Studio Blog

This is great stuff, I am so happy we've gotten this support on Windows when Hyper-V is there. Kudos to everyone involved across borders that made it happen. FYI for anyone using Visual Studio & Xamarin, we've added support for this in Visual Studio 2017 15.8 Preview 1 or higher with the Mobile development with .NET (Xamarin) workload installed. Miguel posted details in this blog post: https://blogs.msdn.microsoft.com/visualstudio/2018/05/08/hyper-v-andro… Happy coding folks. (disclaimer - I work at Microsoft)

On Windows I still prefer the full VS but on OS X Code is great. Full VS is a lot lighter than it used to be. There is a preview of 15 (confusingly, the next version after 2015) available now. "Visual Studio “15” Preview 3 (which is different from Visual Studio 2015 Update 3)" - naming is hard. https://blogs.msdn.microsoft.com/visualstudio/2016/07/07/visual-studio…

Announcing .NET Core RC2 and .NET Core SDK Preview 1 https://blogs.msdn.microsoft.com/dotnet/2016/05/16/announcing-net-core… Announcing ASP.NET Core RC2 https://blogs.msdn.microsoft.com/webdev/2016/05/16/announcing-asp-net-… Announcing Updated Web Development Tools for ASP.NET Core RC2 https://blogs.msdn.microsoft.com/visualstudio/2016/05/16/announcing-up… ----- .NET Core RC2 is supported on the following platforms: Red Hat Enterprise Linux 7.2 Centos 7.1 Debian 8.2 (8.2, 8.3, 8.4)+ Ubuntu 14.04 (16.04 support is coming at RTM) OS X 10.11 Windows 7+ / Server 2012 R2+ Windows Nano Server TP5

That existed on many platforms for a while. Yet, they are getting abandoned. See https://blogs.msdn.microsoft.com/visualstudio/2016/04/06/ui-developmen…

And you didn’t have to pay continuing license fees for use or support. I worked for two companies that used Visual 2008 for years after newer versions came out because we had to support ruggedized Windows Mobile devices and that was the last version that supported it. They just ended support for VS 2008 in April of this year. https://blogs.msdn.microsoft.com/visualstudio/2017/04/10/end-of-suppor…

> ...just to plaster the word AI in more places... I bet that's how the new "AI-assisted" Intellisense in Visual Studio got greenlit: https://blogs.msdn.microsoft.com/visualstudio/2018/05/07/introducing-v… If an AI-infested text editor isn't a sure sign that the bubble is going to pop soon then I don't know ;)

> With the emulator broken Except it's not? Not even remotely true anymore. Starts up instantly now even, they just showed that off. And if you're opposed to Intel HAXM you can now use Hyper-V https://blogs.msdn.microsoft.com/visualstudio/2018/05/08/hyper-v-andro…

I thought it was the other way around? C# on the outside, legacy code connected on the inside? Anyways, I found that confusing. For the rest, visual studio most definitely uses WPF for much of the UI but also the chrome (e.g. see https://softwareengineering.stackexchange.com/questions/75322/which-la… and https://www.quora.com/As-of-2015-how-much-of-Microsoft-Visual-Studio-i… and https://blogs.msdn.microsoft.com/visualstudio/2010/02/16/wpf-in-visual…

There's a glimmer of hope over here [1]. Microsoft updated the XAML Designer. The new designer has support for UWP but note the comments. In particular "WPF [support] will be shipped sometime after the UWP Designer has been released and stabilized." [1] https://blogs.msdn.microsoft.com/visualstudio/2017/09/11/a-significant…

For more information you can check out the blog entry over here: https://blogs.msdn.microsoft.com/visualstudio/2017/10/26/run-book-run-…

Looks like VS 15.3 is official too https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/visual-studio…

Has anyone tried to use visual studio Open Folder feature [1] along the WSL to work in that IDE with big C++ cmake built projects targeting linux? [1] https://blogs.msdn.microsoft.com/visualstudio/2016/04/12/open-any-fold…

/team lead here/ Thanks! Regarding "Scientific" - we just added the Data Science Workload to Visual Studio 2017. Check it out here: https://blogs.msdn.microsoft.com/visualstudio/2017/05/10/build-intelli… Basically Python + Anaconda, R + Microsoft enhanced R, F# with .Net as a single install. Python & R work with any interpreter, including IronPython & Pypy.

IntelliTest[0] is the productized version of PEX. The first release was in Visual Studio 2015 Enterprise edition. [0] https://blogs.msdn.microsoft.com/visualstudio/2015/09/30/intellitest-f…

There's a five part blog series on performance improvements in VS2017 (then codenamed version "15"), here: https://blogs.msdn.microsoft.com/visualstudio/2016/10/14/improved-over…

https://blogs.msdn.microsoft.com/visualstudio/2016/10/11/shorter-solut… Also: https://blogs.msdn.microsoft.com/visualstudio/2016/10/13/faster-c-solu…

They still care about Python. https://blogs.msdn.microsoft.com/visualstudio/2015/08/03/why-write-pyt… https://github.com/Microsoft/PTVS/releases

A smaller and componentized install was a major focus for Visual Studio 2017. There's some more detail here: https://blogs.msdn.microsoft.com/visualstudio/2016/08/22/visual-studio… Smallest install is 500MB .NET/C# install is ~3GB I also believe you won't have to reboot with most installs.

Almost 3 years ago Visual Studio demo-ed a feature that would copy-paste code from StackOverflow, while automatically renaming the variables to fit your code : https://blogs.msdn.microsoft.com/visualstudio/2014/02/17/introducing-b… The tool is available here: https://visualstudiogallery.msdn.microsoft.com/a1166718-a2d9-4a48-a5fd…

From sources in the know: https://blogs.msdn.microsoft.com/visualstudio/2016/10/05/join-us-in-no… Microsoft is going to announce the GA (General Availability) Visual Studio 2016, Team Foundation Server 2016, and Visual Studio Code 2.0 at this connect event in November. Big news for sure…the real question is now that Microsoft is on annual release cadences for their developer tools…will the rapid release cycle move the needle for developers or just cause added frustration…

> Visual Studio should read in all the files, restoring to open the ones I had open last time and allow me to start editing immediately while still loading the rest in the background. It's already done this for a few versions -- a feature named 'asynchronous solution load'. You're able to open a file and start editing while the X hundreds of projects load. However if you do a Navigate To, Find In Files, etc. among other operations, you'll get the modal progress bar because those operations require having the entire solution parsed. But editing and other simple operations are available while the projects are loading (which takes up the bulk of the time). edit: more info about asynchronous solution load: https://blogs.msdn.microsoft.com/visualstudio/2013/10/14/asynchronous-…

I've wondered about this, in the context of generating skeleton Typescript definition files automatically by analysing the source of the library. It appears that Tern (http://ternjs.net/) is the most advanced project for extracting this kind of information from Javascript source files, and can be used as an editor plugin for some degree of intelligent autocompletion. You could also potentially use Esprima (http://esprima.org/doc/) to analyse the AST. The old Visual Studio Javascript autocomplete engine apparently worked in a similar way to what you suggest, running the code in a sandbox and then analysing the types, but they've now moved to a static engine (which I think is also used in VS Code?) - some information at https://blogs.msdn.microsoft.com/visualstudio/2016/04/08/previewing-sa…

This already exists. [1] Except it uses Bing search instead of Stackoverflow. [1] https://blogs.msdn.microsoft.com/visualstudio/2014/02/17/introducing-b…

> I'll take MS's commitment to F# seriously when they stop treating it like a 2nd class citizen. If you're waiting for Microsoft to give exactly equal resources to both C# and F#, you'll be waiting forever. Just like you'll be waiting for equal resources given to Visual Basic, TypeScript, PowerShell, VBA... Equal splits never happen in a competitive situation. 60/40 splits are much more common, but here in this case, we have many first-party languages, so you'd expect a more complicated split, just as we see now. > .NET Core 2.0 is in preview and there is ZERO support for F# with .NET Core in Visual Studio 2017 That's coming in the next update. (https://blogs.msdn.microsoft.com/visualstudio/2017/05/10/update-to-vis… You've been able to run F# in .NET Core in preview form going back to the 1.1 series. My opinion is that .NET Core is the real bag of hurt here, not F#. Stop sticking your hand in that blender. Use Mono and open source F# until .NET Core stops changing the world on each release. > VSCode is no Visual Studio And neither one is Vim. Are we really going to have another editor war? :)

I have run into this problem in two cases: 1. When writing a COM add-in for a host application. When the application wants to shut down, the add-in must release all references to the objects of the host application, otherwise the process doesn't shut down. (At least with the application I'm currently writing an add-in for!) 2. When using out-of-process COM servers such as Excel from another application. This tends to leave lots of "excel.exe" processes running unless you explicitly release everything. See for example: https://www.add-in-express.com/creating-addins-blog/2013/11/05/release… Here is Microsoft describing how they ran into this problem when mixing COM and .NET in Visual Studio, how they solved it using Marshal.ReleaseComObject, how that itself caused other problems later when they combined it with CCW, and ... I'm not sure what their ultimate correct solution was: https://blogs.msdn.microsoft.com/vcblog/2006/09/19/mixing-deterministi… https://blogs.msdn.microsoft.com/visualstudio/2010/03/01/marshal-relea… I am aware of UWP bringing COM back into fashion again, which is why I'm interested in potentially using Kotlin Native with it. :)