Visual Studio for Mac should also provide support for C++. I write android native c++ code on mac, and I think if I can get the c++ developing.

[Voiceover] We're looking at a worksheet called AutoSum.And some of you may know, there's a button on the home tab,far right, called AutoSum,and also on the formulas tab, on the left hand side.Potentially larger here.We can use this in a lot of situations.I'm about to put in a total here.Now I certainly could type equal S-U-M,and put this in manually.Highlight all the data, press return,and nothing wrong with that,but it's going to be a lot faster with this button,and there is a keystroke shortcut as well.Let's first use the button. Mac excel shortcut for sum. You can use iteither on the formulas tab or the home tab,it's makes no difference.

This extension for Visual Studio Code is also available on Windows for the language service experience (code-navigation) portion today. Our current priority for enabling the debugging experience is first Linux (other distros, Ubuntu 14.04 x64 is currently works OOTB), then Mac. On another note we are also working on enabling and improving the Visual Studio acquisition experience which will help with quick installs. A few things you can learn about are talked about at the future of Visual Studio talk at //Build.

Does that help? @Tom, thanks for your feedback:). The way the include path works is really that for includes that we find in the working directory we automatically resolve them, however if you had additional includes say outside the working directory currently the #include for them would be squiggled. To resolve the squiggle we provide a way for you to provide us more details on where this include path is in the ‘c_cpp_properties.json’ file. Once the include path is added our language service can then go and parse the additional includes path specified and populate the symbols to drive code-navigation features.

Does that help Tom? This extension is not working on windows yet?

Even without debugging I want the other features, but, but, but, after install the extension on VSCode 0.10.11 on Windows 7, I got this installation issue too ====================== During installation of C/C++ extension on VSCode 0.10.11 on WIndows 8.1 I received this output: Updating C++ Debugger dependencies Warning: Automated installation is not supported on OS X and Windows. Please refer to C: Users Mike.vscode extensions ms-vscode.cpptools-0.4.2 README.md for troubleshooting information. Finished Warning: Automated installation is not supported on OS X and Windows. Please refer to C: Users Mike.vscode extensions ms-vscode.cpptools-0.4.2 README.md for troubleshooting information. Finished Notice it names OS X and WINDOWS, and provides the full path to a README.md file.

Reading that file provides manual installation instructions for OS X and LINUX. I understand that debugging may not WORK under Windows, but that’s not the same as requiring a manual installation for Windows. Can you arrange clearer messages from the installer if there are future versions before debugging just works?

@Gary, thanks for your feedback. Let me assure you we are certainly not alienating our current Windows users and Windows remains our top priority platform. At //Build this year we gave a talk w.r.t.

The new things Visual Studio 2015 brings for C++ developers on Windows(). Given C++ is a cross-platform language and with the rise of mobile apps and such many existing Windows developer we understand are also developing for other platforms (Linux, Mac, iOS, Android etc.). The work we are doing with VSCode – C/C++ extension is to provide cross-platform C++ developers a great tool of choice for their edit-build-debug cycle with the same consistent look and feel across all platforms. In addition to this all the feature work that we have done so far except debugging works across the board for Windows, Linux and Mac. Our current thinking for bringing up debugging first on Linux and then Mac has been because we feel Visual Studio Community already provides a pretty nice debugging experience for C++. I hope this helps you understand our thinking a little, if you feel we are missing something and you can spare some time, we would love to get in touch with you. You can reach me at:).